Workflow prioritization

To ensure that workflows run efficiently and successfully, workflows are prioritized depending on how the workflow is triggered.

Order of priority for starting workflows

Priority	Workflow Trigger	Description
1	User actions and request offering workflows	The workflow is run on the object's page, or object's record details page, or when the workflow is rerun. Example From the menu, click Hardware > All Assets. Select all, or one or more records. Click Run Workflow. Object details From the menu, click Hardware > All Assets. Click an asset record.  Click Available Workflows, select and then run the workflow.
2	Data entries	User changes an attribute in a record that triggers a workflow.
3	API calls	Changes caused using the Import feature or synchronizing an integration.
4	Scheduled workflows	If you have multiple scheduled workflows, you can choose the level of priority or sub-priority.  That is, scheduled priorities will still run after workflows triggered by user actions, data entry, and so on - not matter what sub-priority you select. Let’s say you have multiple scheduled workflows that run in the same time frame. One of the scheduled workflows is business critical, such as locking the devices of users who are being offboarded, you can set the priority of that workflow to Urgent. For workflows that run in the same time frame, that aren’t business critical, you can set them to Low or to the default setting which is Medium.

Checking the status of workflows