I've been building and testing a workflow designed to be triggered through a button click. Previously, when I click a button on the app, the workflow will keep saying "running WORKFLOW_NAME" with the running time until the workflow finishes running.
However, since a couple days ago, when I click the same button, the "running WORKFLOW_NAME" message only runs for less than 2 seconds, and according to the console, the workflow has finished running. But when I checked the workflow run history for the same run, it takes about 40-50 seconds to actually finish.
Bringing this up again as this issue is our major roadblock in presenting this POC to our stakeholders. This also got me worried in the reliability of Retool as fixing a major component like Workflow would take so long. Is it possible for us to jump on a call so we can investigate which part has gone wrong?
Hi @brianzjj thanks for checking in & sharing how this is impacting your team. There was a bug fix for a related issue that went out on v3.36.0, but it sounds like this must be a separate issue.
The return block should ensure the workflow is run synchronously from the app Could you share an export of the workflow so that I can investigate further with our team? or, if you can't share an export with us, post screenshots of the return block & app trigger?
I'm not able to set up a 1:1 call, but if we haven't sorted it out by tomorrow, I'd like to take a look in office hours if you're available to join
Thanks so much! I recreated a very similar flow in my own Retool org, but I have not been able to reproduce this yet I'm also not finding other reports of this issue, so I'll need to get more information in order to get a fix. Can you confirm what version # you're on (click on the question mark in the bottom right corner of any app)?
Long shot, but any chance the latest deployed version of the workflow doesn't have the webhook return connected to your workflow?
It seems like discussing this in office hours or sending us a JSON export would be helpful as a next step.
Hi @brianzjj I'm still in the process of looking into this & looking to hear more from our Workflows team, but wanted to check in in case it's helpful, it seems like it could be related to the branch block. If I remove the connection to the branch block, I'm able to get it working as expected. Again, still continuing to look into this further!
Just want to touch base and see if there is any progress on this. I can't think of a workaround for the branch block, and I also want to keep using the block as I expect there will be more branches from that branch block.
Hi! @Tess
I'm having a similar issue with my workflows when executing it from a trigger or Retool App. The Workflow ends successfully but skip every single step after my Branch Block.
When I run manually from the workflow with the same test data from the trigger, the workflows branch block runs correctly.
Logs for the workflow running from trigger from the app doesnt show anything strange in the branch block just skip every other step.