How can an admin access details about a failed orchestration?

Accessing details about a failed orchestration is essential for troubleshooting and understanding why the orchestration did not complete successfully. The most effective way an admin can find this information is through the "Paused and Failed Flow Interviews" section in the Setup.

This area provides specific insights related to failed orchestration instances, enabling the admin to review error messages, inputs at the time of failure, and possibly the flow path taken. By examining this data, the admin can identify the root cause of the failure and make necessary adjustments to the orchestration.

Other options, while they may provide valuable features or tools, do not specifically focus on failed orchestration details. For example, the App Launcher is primarily a navigation tool to access various applications, Flow Designer is used for creating or modifying flows, and the Orchestration Monitor tracks orchestration runs but does not provide detailed error messages or specific details on failures. This makes "Paused and Failed Flow Interviews in Setup" the most direct and informational resource for an admin to access information about failed orchestrations.