Pipeline Change History
Each pipeline keeps an immutable, time-ordered history of every configuration change, showing what changed, when it changed, and who made the change.
As pipelines grow more complex - and more people touch them - it gets harder to answer simple questions: What changed? When? And why did things break? Without a clear record, teams often end up guessing, scrolling through Slack, or retracing steps by hand.
Pipeline Change History adds long-overdue visibility into how your pipelines evolve over time, without changing how you manage them today. It shows a complete, time-ordered history of every configuration change made to a pipeline.
Any update - adding or removing tables, adjusting flush rules, toggling history mode, or changing settings - is automatically recorded. You can see exactly what changed, when it changed, and who made the change, all in one place.
This history is immutable and always available, giving teams a reliable source of truth for pipeline configuration changes.
Why this matters:
- Quickly pinpoint configuration-related issues during debugging
- Improve collaboration across teams managing shared pipelines
- Eliminate guesswork around “what changed last”
- Maintain an audit trail for compliance and internal reviews