Workflow (code flow) executions stuck in "queued/pending" for several minutes before starting
Workflow: "Trustpilot Service Review Reply" (Workflow Builder code flow). Trigger: ticket-updated (public agent reply on Trustpilot service-review tickets). It posts the agent's reply to the Trustpilot API.
Summary of the issue: Executions are spending a long and highly variable amount of time in the queued state before a runner picks them up and begins execution. The delay is entirely between the Workflow execution queued event and the Starting workflow execution event. Once an execution actually starts, the workflow logic - including the outbound Trustpilot API call - completes quickly (typically well under 1.5 minutes, with the API call itself taking a fraction of a second). This points to execution scheduling / queue pickup latency on the platform side rather than anything in the workflow code or the third-party API.
Business impact: The customer reply is only sent to Trustpilot once the execution starts (not while it is queued). So any time spent queued is pure delay before the reply appears on Trustpilot. We are seeing waits ranging from ~6 minutes to ~36 minutes, which is not acceptable for timely public review responses.
Execution id f9817f1b
Workflow execution queued: 10:17:44.651Starting workflow execution: 10:54:07.134- Queue wait: ~36 min 23 sec
- After start: Trustpilot reply posted 10:54:09.650 (≈0.3 sec after the posting step began), completed 10:55:18 (total run ~1 min).
Request: Please investigate why these workflow executions sit in the queue for several minutes (up to ~36 minutes) before a runner begins processing them. Specifically: is there a queue backlog, concurrency/throttling limit, or worker capacity constraint affecting code flow execution pickup? We'd like to understand the expected queue-to-start latency and how to reduce it, as the queued time directly delays our customer-facing Trustpilot responses.