Examining a Try scope's output for debugging data
One other advantage of using scopes is that you can access the scope's own result status to see whether there is any problematic code within that section. That is useful when you want to test a section of your logic app you are unsure about or think of as unreliable.
To simulate this, I've amended our exercise. Scope 3 has been moved to the top of the logic app and simply renamed scope, for clarity. Within the scope, I have added a Terminate action of Failed (this can be found in the Control section of the Dynamic catalog). The new scope now looks like this:
When I run this, the Terminate action will force a failure at this point. As an action within the scope has failed, the entire scope will be marked as failed.
Failure is a good and useful process. Logic apps should be tested both for their success as well as how they...