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 action |
The workflow is run on the object's page, or object's details page, or when the workflow is rerun. Examples Object page
Object details
|
2 | Data entry
|
User changes an attribute in a record that is associated with a workflow. |
3 | API calls | Changes caused using the Import feature or synchronizing an integration. |
4 | Schedule | The workflow is run by a schedule. This includes running the scheduled workflow in the workflow builder. |
Example
Action 1: A scheduled workflow is started that updates all user records in the People view.
Action 2: At the same time, an administrator makes a change to a user record in the People view and runs a workflow manually.
Action 1 has a priority of 4 because the workflow is triggered by a schedule. Action 2 has a priority of 2 because the workflow is triggered by data entry.
In this scenario, action 2 is started before action 1 because it has a higher priority.
Checking the status of workflows
Comments
0 comments
Please sign in to leave a comment.