Skip to main content

What does [in queue] in the workflow execution history mean?

In the execution history page and the monitoring page of the workflow, you can see the number of workflows in queue, which indicates that a number of workflows have been triggered but need to be queued up to wait for execution.

  • Execution History Page

  • Monitoring Page

Why workflow in queue occurs?​

Whether the workflow is serial or parallel, it is possible to have a workflow in queue.

  • Serial workflows will be in queue is because that only one instance can be executed at a time due to the characteristics of the workflow, and if there are too many triggered workflows to be executed instantly, there will be a queue waiting to be executed.

  • Parallel workflows will be in queue probably because the current server resource usage enables automatic optimization for batch workflows, which need to be queued for execution.

:::Tip

As workflows across the network rely on a unified service, after a workflow is triggered, it has to be queued for execution in the public queue in order. At this point, there may be no queuing in the backend of your organization, but there may be workflows in queue in other organizations.

:::

Impact on Workflow​

  1. If Admin finds an exception in a workflow, Admin can pause the consumption. At this time, the user can still trigger the workflow, and the number of workflows in queue in the execution history page still increases. Number of workflows in queue = Number of workflows in queue before pause + Number of newly triggered workflows after pause.

  2. For the same record, at a time there is only one workflow in progress allowed. If you trigger a record multiple times while paused, it will still be executed only once after resuming execution.

Have questions about this article？ Send us feedback