The ability to track version history for routing workflows, including manual annotations, automated change summaries, and modification timestamps with user attribution.

Currently, when workflows are modified, there's no clear record of what changed, when, or by whom. If multiple admins are working on routing logic and something breaks, it's nearly impossible to identify what changed or roll back to a working version. This creates risk, especially in complex environments where routing directly impacts revenue.

For example: if three admins are managing routing workflows and someone makes a change on Friday that breaks EMEA routing by Monday, there's no way to quickly identify what changed, who changed it, or restore the previous working version. Teams end up rebuilding logic from memory or screenshots, which wastes time and introduces errors.

Version control would allow tracking each modification as a numbered version, with manual notes from the person making the change ("Updated country filtering"), an automated diff showing exactly what changed (which nodes, conditions, field mappings), and a timestamp with the modifier's name. This would enable quick troubleshooting, rollback capabilities, and compliance auditing for routing changes.