Last Updated on March 1, 2022 by Rakesh Gupta
Big Idea or Enduring Question:
- How to debug In-Progress Flow Orchestration?
After reading this blog, you’ll be able to:
- Debug in-progress Autolaunched Orchestration (No Trigger)
- Debug in-progress Record-Triggered Orchestration
Business Use case
Jestilla Zetkin is working as a System administrator at Gurukul On Cloud (GoC). She has created an Autolaunched Orchestration for the employee onboarding process. She wants to learn how to debug an in-progress flow orchestration.
Guided Practice (We-do):
Unlike a screen, Record-Triggered, or other flows, there’s no Debug button in Flow Builder for orchestrations. It is a little bit tricky to debug a flow orchestration.
You can debug information about an in-progress orchestration to understand better the path an orchestration takes with different scenarios and the variable values at points in the automation. As of Spring’22, Salesforce allows you to debug In-progress, failed orchestration however you can’t debug a completed orchestration.
As far as you have at least one Interactive Step, the orchestration will pause, and you can click Debug Orchestration to debug it. If you don’t have anything to stop the run from rushing through to completion, you won’t have a way to inspect intermediate values.
To debug an in-progress flow orchestration, perform the steps below:
- Navigate to App Launcher and click on the Orchestration Runs.
- Debug Orchestration the In Progress orchestration by selecting the dropdown next to it.
- It will open Flow Designer for you. Orchestrator currently shows, for each step flow, the inputs that went into it and the outputs that came out of it.
I want to hear from you!
What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.