Hi, I was building a workflow in Process Studio and got curious about something what actually happens when a step fails in the middle of execution? Like if I have 5 steps and step 3 breaks, do the changes from step 1 and 2 already get committed, or does everything stop and reset? Also is there any way to capture which rows caused the failure and still continue processing the remaining ones? Would love to know how others are handling error scenarios in their workflows.
To prevent a single failing row or step from killing the entire workflow, you have three main options, depending on the level of control you need:
1. Step-Level Error Handling (Best for Row-Level Failures)
Most transformation steps in Process Studio allow you to redirect failing rows to an alternate branch instead of stopping execution.
-
How to configure: Right-click the step causing errors (e.g., REST Client, Database Lookup, Set Values) and select Define Error Handling…
-
Target Step: Point the error hop to a target step (like a Write to Log step or a file error log).
-
Error Fields: You can capture the error code, error description, failing field name, and number of errors into new fields to handle downstream.
2. Standard Error Flow Control (Continue On Error)
For high-level orchestration processes (.psp files), you can dictate path execution using conditional hops:
-
Unconditional Hop (Black): Executes regardless of success/failure.
-
Error Hop (Red): Follows this path only if the previous step/workflow fails, allowing you to trigger error loggers or cleanup routines without crashing the parent process.
3. Continuation Logic inside Child Workflows
If you are iterating over rows (e.g., using a Job/Process Executor or running child workflows in a loop), set the step execution to continue processing subsequent rows even if an individual execution returns an error.
