Matt Silverlock
CDCloudflare Developers
•Created by ajay1495 on 3/19/2025 in #workflows-beta
Right, we should have expected retry
I'm sorry - what is your ask? What I said above still applies:
If the Workflow is showing as terminated - the step showing as “running” is a bug we’re fixing. The fix won’t be retroactive.You then said:
The workflow was stuck in a running state and it wasn't timing out and retrying.My understanding is thus the steps are (incorrectly) showing as running, which is a metrics/metadata bug, but the instance is now terminated. What is not clear is whether this is still occurring? We fixed a number of metadata/state bugs, including cases like these.
15 replies
CDCloudflare Developers
•Created by ajay1495 on 3/19/2025 in #workflows-beta
Right, we should have expected retry
If the Workflow is showing as terminated - the step showing as “running” is a bug we’re fixing. The fix won’t be retroactive.
15 replies
CDCloudflare Developers
•Created by ajay1495 on 3/19/2025 in #workflows-beta
Right, we should have expected retry
Are these still showing as running?
15 replies
CDCloudflare Developers
•Created by Boragorn on 3/25/2025 in #workflows-beta
workflow create batch issues
Can you provide more details? What is your account ID? What is the overall state of all of the Workflow instances?
34 replies
CDCloudflare Developers
•Created by ajay1495 on 3/19/2025 in #workflows-beta
Right, we should have expected retry
@ajay1495 What is your account ID?
15 replies
CDCloudflare Developers
•Created by ajay1495 on 3/19/2025 in #workflows-beta
Right, we should have expected retry
cc @Diogo Ferreira
15 replies