How does a try scope handle errors in a flow?

• A. It acts like a private flow inside the parent flow.
• B. It cannot have its own error handling.
• C. Unhandled errors bubble up to the parent flow.
• D. It always runs in a separate transaction.

Answer: (A)

A try scope creates an error boundary inside a flow, so error handling can stay localized. The code inside the try runs, and if an error occurs, control moves to the catch block within the same try scope, allowing you to handle the issue right there—like a private sub-flow inside the parent flow. This containment lets you log, transform the payload, or take recovery actions without disturbing the rest of the flow. If an error isn’t caught within the try scope, it can bubble up to the outer flow so a higher-level handler can deal with it. The try scope itself doesn’t inherently mandatorily run in a separate transaction.