"Scheduling Failure" when running a workflow after making edits

I have a workflow that has multiple steps (around 20). Typically, the workflow takes about 30 seconds to complete. But last night whether clicking Run from the editor, or triggering the workflow from a retool app, it always ends on the startTrigger with "Scheduling Failure," shows no logs, and shows 0ms for the startTrigger run.

When duplicating the workflow, it works perfectly on multiple runs until i make any edit, even a test edit of adding a space, etc to a string, and then the bug reappears. I can't get insight into what the issue is and haven't found other posts about scheduling errors except one from someone who was self hosting retool (I'm not self hosting). In the screenshot you can see a successful run followed by several unsuccessful runs, and then another screenshot showing the 0ms start trigger stops. Also when clicking start trigger to view logs, it just shows a spinning wheel forever

NOTE/EDIT: Oddly, if i use any runs as test json and click "run with previous blocks" on my final blocks, they always run no problem. the issue only appears when clicking "run" or triggering the workflow


By the way, when deleting all blocks but one and editing it to just return "hello" it still fails and says "Scheduling failure" when running from the workflow editor or anywhere else

Update: I've tried recreating my workflows several times in different configurations and no matter what the same issue keeps happening

Hey @dg_si4c - thanks for reaching out. That is definitely some odd behavior. Is this happening with all your workflows or just the one?

As you mentioned, this is an error that I almost exclusively see for self-hosted users as it indicates that Retool is unable to communicate with the Temporal service. On cloud, this should always be configured for you. Do you see any errors in your browser console when this happens?