In the Workflow Editor, you will find an “Enable option to run in high priority” toggle located in the Action “…” dropdown. This toggle is disabled by default.
When activated, this toggle introduces a “Run in high priority” button at the bottom of the Execution page. Selecting this option during workflow execution allows you to manually prioritize the workflow, ensuring it is processed with higher urgency when necessary.
This feature is designed for situations where certain workflows need to be prioritized for optimal operation.
FAQs
If I set several workflows to high priority, how are these high-priority workflows organized?
When any workflow starts, it goes to a queue (first in, first out). We have two queues: one for high-priority workflows and another for non-high-priority workflows.
What happens if non-high-priority workflows are processing and a high-priority one launches? Will it put the non-high-priority ones on hold, or does the one in progress finish first?
The Traffic Manager handles queue management and cannot stop or hold any running workflow. It can only start a workflow. Therefore, if a high-priority workflow launches while a non-high-priority one is in progress, the non-high-priority workflow will finish first before the Traffic Manager checks the high-priority queue to start the next workflow.
Do high-priority workflows take precedence over everything else, including small non-workflow actions?
High-priority workflows are prioritized, meaning that when a workflow is completed, the Traffic Manager first checks the high-priority queue. If there is a workflow there, it will start it. If there are no workflows in the high-priority queue, it will then check the non-high-priority queue. Small non-workflow actions may not be affected directly by this prioritization, as the Traffic Manager focuses on workflows specifically.