Every handoff that passes a value, status, or control from one connected action to another needs an explicit test. Handoffs that rely on input variables deserve particular attention, while failed runs require a separate diagnostic check because run history can identify the failing action.
Handoffs that need explicit testing
| Handoff | What the test needs to establish |
|---|---|
| Output from one action to an input on another | The receiving action receives the intended value rather than merely appearing to be connected. |
| Input variable to a later action | Values are supplied for the input variables the flow actually uses. |
| Passed value to a conditional route | The value produces the intended downstream action or route. |
| Completed action to the next action | The workflow advances from the expected completion point. |
| Failure to diagnosis and recovery | The failing action is located, its root cause is corrected, and the flow is then turned back on. |
How to run the check
Each handoff should be treated as a separate test case. A visible connection does not by itself establish that a value or completion signal crossed the boundary correctly.
For a variable-driven handoff, the flow creator should enter values for the input variables that the flow uses and then select Run flow. The check should record which handoff each value exercises and whether the expected receiving action follows. Where different values lead to different routes, the relevant routes should be exercised separately.
If the flow fails, the cited troubleshooting guidance recommends opening its run history to find the failing action. The root cause should be fixed before the flow is turned back on.
What still needs confirmation
The cited guidance supports testing with input-variable values and diagnosing failures through run history, but it does not establish a universal successful-handoff standard. Tool-specific permissions, retry behavior, field constraints, connector compatibility, and operational limits are not verified here. A small team must confirm those details in the relevant tool documentation and define the expected result for each handoff before treating the integration check as complete.