Function Versions & Rollback
What happens when you edit a custom workflow's code, and why an edit can't permanently break it.
Each action inside a custom workflow keeps a version counter that increases every time you edit its code from the Advanced view. The current version number (for example, v3) is shown alongside the action's other details.
Earlier Versions Are Kept
Saving a new version doesn't discard the one before it — earlier versions of an action's code are kept, not overwritten. That means editing a workflow's code is not a one-way, destructive operation: if a change turns out to be wrong or breaks something the action used to do, the version that worked is still there.
You don't need to be overly cautious about editing an action's code to get it right the first time. A version that breaks something isn't a dead end — the working code that came before it hasn't gone anywhere.