# What should I do when workflow branches return different output fields?

Canonical URL: https://help.iagenify.com/faqs/workflows/what-should-i-do-when-workflow-branches-return-different-output-fields

[← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)

HELP CENTER · FAQ Workflows 2 min read
# What should I do when workflow branches return different output fields?
Give later steps a predictable input shape. Normalize branch results or add explicit conditions so each path handles fields that may be absent.
IaGenify
Workflows

## Understand each branch's output
A conditional path may run a different set of steps, so the final output can contain different fields depending on the branch. Inspect successful runs for every path and list which values each one produces. Do not assume that a field seen in one run will exist for all other inputs.
Choose which values downstream steps truly require and define what should happen when a branch does not produce them. A missing optional value may be acceptable; a missing identifier needed for an update should stop or redirect the path with a useful explanation.
## Make the handoff explicit
Where possible, have each branch return the same named fields and compatible types. When a value is not relevant on one branch, represent that absence deliberately and guard any step that requires it. This keeps later mappings readable and reduces failures caused by an implicit assumption.
Test at least one input for each branch, including boundary cases that choose a different path. Inspect the downstream step's actual inputs, not only the branch condition. If the workflow changes later, repeat those path checks so a new branch does not quietly break existing mappings. [← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)