You are here:
View Details for a Failed Orchestration Run
Troubleshoot a failed orchestration, and gain insights about why it failed. You can view failed orchestration run details within 14 days of it failing.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Troubleshoot a failed orchestration, and gain insights about why it failed. You can view failed orchestration run details within 14 days of it failing.
| View supported editions for Flow Orchestration. |
| User Permissions Needed | |
|---|---|
| To access the debug action for a running orchestration: |
|
Sharing must be enabled for orchestration runs and flow interviews.
If you started running an orchestration before upgrading to Spring ’22, stage and step instance IDs are shown as null in orchestration debug information. Evaluation flow output is also shown as null.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.