I have a longer workflow that should span over several days with various loops and delays. The flow runs until the first delay and then triggers an internal error. I am unable to access the run under “runs”; it does not open, so my suspicion is that the issue lies with the delay function.
I think it might be a log size issue. Could you please let me know if the flow executes successfully? For example, do you see the results in your apps?
Thank you for addressing the problem. I’m not sure if it’s working correctly. This morning there was another internal error, and now when I restarted the task, it executed three times! (I’m not entirely sure, but I suspect the webhook was triggered multiple times by my system). I’ll let you know tomorrow if the task changes from paused to internal error, or if the tasks are now being executed correctly.
Hi @abuaboud
I tried on several scenarios, and the delay option always causes the same internal error. I tried a scenario with 10 minutes, 1 hour and several hours.
So there is definitively a bug.
The version I have is V0.3.6
Thanks in advance for your help!
I tested it again. It seems that the “delay” function works in principle. However, in my case, there are 3 delays built into a loop. Could that be the reason?