# How can I make a workflow's data transformations traceable?

Canonical URL: https://help.iagenify.com/faqs/workflows/how-can-i-make-a-workflow-s-data-transformations-traceable

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

HELP CENTER · FAQ Workflows 1 min read
# How can I make a workflow's data transformations traceable?
Name transformation steps clearly, preserve the source identifier, and record the key input and output needed to explain each result. A useful run history should let an operator trace a changed value back to the step that produced it without exposing unnecessary sensitive data.
IaGenify
Workflows

## Keep provenance with each item
Carry a stable record ID or event ID through the workflow so later steps can be connected to the original input. When a step filters, maps, or combines data, retain enough context to explain which source records contributed.
Record transformation versions or rule names when business logic changes over time. This helps explain why two runs produced different outcomes and supports review when a downstream result is challenged.
## Log for diagnosis without leaking data
Store concise status, counts, identifiers, and error details rather than copying full confidential payloads into logs. Apply access controls and retention limits to run history just as you would to the source data.
Test traceability with a sample that exercises normal, filtered, and failed paths. Confirm that you can reconstruct how a final value was derived and identify the responsible step while respecting privacy requirements. [← Back to Workflows FAQs](https://help.iagenify.com/faqs/workflows)