You are here:
Running Context of an Orchestration
The running context determines the access that an orchestration has to Salesforce data and the context used by a paused orchestration to resume. By default, the running context of an orchestration is the Automated Process User in system context.
Required Editions
| View supported editions for Flow Orchestration. |
The default running user for an orchestration depends on the type of orchestration and the API version that it runs in.
Autolaunched Orchestration
For API version 60.0 and later, an autolaunched orchestration always launches and resumes in the context of the Automated Process User in system context.
For API version 59.0 and earlier, an autolaunched orchestration usually launches in the context of the user who launched the orchestration. If the orchestration is launched from Apex, it runs in a system context. Control the context that an autolaunched orchestration launches and resumes in with the How to Run the Orchestration advanced option.
For API version 59.0 and earlier, the context that a paused, autolaunched orchestration resumes in depends on how it was launched or what caused it to resume.
| Scenario | Resumes In |
|---|---|
| Started in system context | System context |
| Resumed by a manually published platform event | The context of the user who published the platform event in system context |
| Resumed because an asynchronous background step was completed | The same context it ran in before the asynchronous background step |
| Resumed because a MuleSoft step was completed | The context of the Automated Process User in system context |
| Resumed because an interactive step was completed | The context of the user who completed the interactive step in system context |
| Resumed because an entry or exit condition was met when a record changed | The context of the Automated Process User in system context |
Record-Triggered Orchestration
For API version 60.0 and later, a record-triggered orchestration always launches and resumes in the context of the Automated Process User in system context.
For API version 59.0 and earlier, a record-triggered orchestration always launches in the context of the user who triggered the orchestration in system context.
For API version 59.0 and earlier, the context that a paused, record-triggered orchestration resumes in a user in system context. The user that the record-triggered orchestration resumes as depends on what caused it to resume.
| Orchestration Resumed as a Result Of | User |
|---|---|
| A manually published platform event | The user who published the platform event |
| An asynchronous background step was completed | The same user that the orchestration ran as before the asynchronous background step |
| A MuleSoft step was completed | The Automated Process User |
| An interactive step was completed | The user who completed the interactive step |
| An entry or exit condition was met because a record changed | The Automated Process User |
