Navigation

    OpenIAP

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    "EnsureNoderedInstance completed"???

    General Discussion
    2
    7
    20
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Colby Cruwys last edited by

      When I try to start Nodered, I am getting this error:

      Step 3.PNG

      I don't understand the message or how to rectify the problem?

      Allan Zimmermann 1 Reply Last reply Reply Quote 0
      • Allan Zimmermann
        Allan Zimmermann @Colby Cruwys last edited by

        On app.openiap.io or a self hosted openflow ? If app.openiap.io, did you try with the same user as your did this post with ?

        C 1 Reply Last reply Reply Quote 0
        • C
          Colby Cruwys @Allan Zimmermann last edited by

          Hi @allan-zimmermann, yes it's the same user and I'm using your app,openiap environment. Just now I've rebooted my machine, restarted OpenRPA which has connected correctly:

          1. OpenRPA Linked.PNG

          I've logged in with my cruwys at gmail address and tried starting a node-red instance but it just leads to that same "EnsureNoderedInstance completed" screen. When I try visiting the node-red instance anyway I get this:

          4, Attempt to open.PNG

          Quite confused. I don't know if it's related but when I log in to OpenFlow I get a whole bunch of idle WorkFlows that won't end because those noderd flows I wrote had the form setting as "idle" instead of "complete":

          6. Open Flows.PNG

          Allan Zimmermann 1 Reply Last reply Reply Quote 0
          • Allan Zimmermann
            Allan Zimmermann @Colby Cruwys last edited by Allan Zimmermann

            @colby-cruwys I just found a small issue where admin could not start a NodeRED, but i could not reproduce the error for normal users. But just as you wrote a pushed a fix for that issue, and when I impersonate your user after the fix, I can start a NodeRED just fine. Could you please try again and see my fix also fixed your issue or if it's still there for you ?

            Allan Zimmermann C 2 Replies Last reply Reply Quote 0
            • Allan Zimmermann
              Allan Zimmermann @Allan Zimmermann last edited by Allan Zimmermann

              The list of un completed tasks is not related.
              Those are there either from

              1. you not adding a "workflow out" node that updated the status to successful or failed
              2. you are not catching errors using the "catch" node and updating the workflow state with the error/setting state error
                6736c368-e575-42fb-928d-578bf69a4383-image.png
              1 Reply Last reply Reply Quote 0
              • C
                Colby Cruwys @Allan Zimmermann last edited by Colby Cruwys

                It works perfectly now: Thank you so much 🙂

                EDIT: Regarding the Idle Workflows, they were from testing...but I will play with those test flows and try and end them.

                Allan Zimmermann 1 Reply Last reply Reply Quote 1
                • Allan Zimmermann
                  Allan Zimmermann @Colby Cruwys last edited by Allan Zimmermann

                  @colby-cruwys tip, if its just tests, then you can find all workflow instances in the the workflow_instances collection. So you can just delete them there. ( https://app.openiap.io/#/Entities/workflow_instances )

                  1 Reply Last reply Reply Quote 1
                  • Locked by  A az 
                  • First post
                    Last post