On self-hosted retool, version 3.148.0-stable
Have also tried 3.178.0-edge, the problem still persists
In short - when the wait time is under 60s, the block will wait for the time specified. When the wait time is over 60s (regardless of whether seconds, minutes or hours are specified), the wait block terminates immediately.
See screenshot: there is only 1 second time delay between wait1 and code1
(The wait block in this example is configured to wait for 63 seconds)
@Ben01,
Ah! Retool is not managing your temporal.
When this fails, can you send me your retool backend workflow and worker logs and share your temporal logs with me?
Thanks,
I've attached log lines from workflows-worker and workflows-backend
(I've had to name the file .json because this forum won't allow .txt upload)
The logs begin from the moment I click the "run" button on the workflow we're discussing and end when it stops (a few seconds later)
Ben, sorry, I also need the Workflow Run Id from the logs that you sent me (the logs you sent have several workflow Run Ids in them). So if you know exactly which run that was, you can in the bottom left corner of your workflow when you click Run history.
If you're unsure of of which run it was, you can send me the Workflow Run Id from several of them that you think it might be and I can look for it in your logs. Otherwise, run again, get the WorkflowRunId and send me new logs.
Also, do you by chance have any temporal logs you can share with me?
Thanks!