Hi all, I'm having an issue with a task that has a manual_only trigger, when I resume said task it only resumes after ~10 mins when the Lazurus process picks it up. I would have expected it starts straight away. It works fine if I run the flow on my local machine however if I run it in the cloud then it becomes an issue. I've tried adding a LocalResult to my flow but this hasn't worked, here is a pastebin with a very simple flow so hopefully you can reproduce the issue: https://dpaste.com/9DRBEHZXK
j
josh
08/25/2020, 12:10 PM
Hi @William Smith I am unable to reproduce your issue using the snippet provided š¤ after clicking resume the task is picked back up and run for me
Let me ping someone on the team to see if anyone has encountered this behavior
w
William Smith
08/25/2020, 1:13 PM
Hmm, how odd, yeah I'm seeing this behaviour consistently
Thanks for posting the logs Iām going to elevate this to the team š
w
William Smith
08/25/2020, 1:32 PM
Great, thanks
j
Jenny
08/25/2020, 6:10 PM
Hi @William Smith - Thanks for raising this. It comes from flow concurrency limits in the Developer tier but is not intended behavior. The fix is a reasonably complex but we're going to prioritize it. For now, that roughly ten minute delay to resume a paused task is expected.
w
William Smith
08/26/2020, 8:14 AM
Ah OK, well at least it can be reproduced. Will look out for the fix. Thanks