2 workflows calling agents stopped running

💬 Agents
,
1

Hi there, I'm bringing another piece of info to the thread as I was about to create a new topic with a very similar issue.

Maybe it is linked, maybe not but happy for the retool team @ChiEn to move that message to a new thread if it appears to be 2 different issues.

So we have 2 workflows that stopped running this week, when investigating them we noticed that both were in a pending stage for the last 2 days.

These are the only 2 workflows calling agents so I believe it might have to do with an agent being called.

  1. We tried to terminate the workflow and that didn't work, the button is just stuck
  2. We tried running the flow again and it returns an error "Workflow run failed to start. Please try running it again."
  3. We then tried copying the workflow, but launching the new one just returns the same error "Workflow run failed to start. Please try running it again."
  4. We tried doing an export / import of workflow as well and that always returns that same error

One of our workflow was very small, so we rebuilt it from scratch as a test and that worked and it is now running again, we deleted the old one that was stuck.

However the second workflow has quite a few complex blocks and if possible we'd like to avoid rebuilding it from scratch unless we don't have the choice. Could you please help us unblock that workflow as well? and you might want to also investigate why that workflow is never ending and crashing on reset.

Again these are the only workflows with agent blocks inside, we have another 25+ workflows running and none of them stopped.

That workflow has been running hundreds of times in the past and includes waiting time up to 30-40min depending on scenarios and it never got stuck so maybe our scenario is a bit different.

Instance: https://angsanatools.retool.com/
Workflow: be013be7-7a97-4140-9f0e-6bdff958185e

Many thanks
Je

EDIT 1: We were able to get that workflow unstuck by:

  1. Deleting the agent blocks inside the workflow that we believe were the issue
  2. Exported the workflow as JSON
  3. Deleted the workflow
  4. Imported the workflow with the saved JSON
  5. Added the agent block again
  6. Got a successful run

Of course assuming this is a related issue based on the initial message above, but we definitely couldn't get that workflow unstuck either - so hope this helps

2

Hey @Jeje, thanks for reporting this. I split your post into a new topic under the Agents category since you suspected this might be related to the Agents blocks in your workflows. We currently have a ticket open about the terminate button not responding, and I’ve added a +1 to that ticket for you. Really appreciate your detailed testing and updates about Agents being the potential issue. I’ll look more into this! :pray:

3

Hey @Jeje, have you tried running the workflows that call Agents again? If so, how did they go? Did you see any error logs in the workflow run details or any messages in the browser console when the failure occurs?

4

Hi @ChiEn sorry just seeing this, thank you for moving the post.

No errors since we unstuck the workflow by following steps 1 to 6 in my edited message (bottom part) and also no issues with the other workflow we've rebuilt from scratch. So hopefully a one-off issue with those agent blocks!

5

@Jeje Of course, happy to help! Our engineering team is looking into the Workflow Terminate button getting stuck. I’ll keep you posted as soon as I have an update. In the meantime, please let me know if it happens again.

Also great to hear the Agents blocks are working now. A fix went out recently and we’re continuing to improve them, so let us know if you spot anything else! :pray:

1 Like