Introduction

Workflows connected to Orchestrator can get into a queue. For example, you may have one Bot Runner assigned to multiple workflows, and those workflows, in turn, may have the same scheduled start time. Multiple workflows cannot be run simultaneously by the same Bot Runner, so they will get into the queue.

Principles of queueing

1. If the workflow is scheduled:

   1. The system looks for all the Bot Runners with an "online" status, which are assigned to this workflow.

   2. The first "online" Bot Runner executes the workflow.

   3. If all of the Bot Runners are busy, the workflow goes into a queue. If the workflow already exists in the queue, it won't be put into the queue again.

2. If the workflow is run by a click on the "Run now" button:

   1. The selected in the drop-down list Bot Runner executes the workflow.

   2. It is impossible to select a "busy" or "offline" Bot Runner in the drop-down list.
3. If the workflow is run by the webhook-link:
   1. In this case, the principle will be the same as in the case of the schedule, with the only difference that if the same bot is already in the queue, and some parameters are passed to the new bot to be launched, that new bot will still be added to the queue.
4. If the workflow is run by the API:
   1. In this case, the principle will be the same as in the case of the webhook-links.

Launch management

Workflows in the "In queue" and "In progress" statuses can be seen on the "Run history" page in the "Workflows" and "Bot Runners" tabs. If you want to cancel the execution of the workflow, you can perform the following actions:

1. Delete the workflow from the queue. To do that, click on the symbol by the corresponding workflow:
   
2. Perform a "soft-stop" or a "hard-stop" of the workflow. To do that, click on the required symbol: