Workflows version history
Early Access release
Version history in Okta Workflows provides a record of changes that were made to a flow over time. Each time you save a flow, a new version is created. Use version history to audit changes, view execution history for specific iterations, and restore a flow to a previous state.
How it works
Okta Workflows tracks versions at the flow level. When you open the Version History tab within a flow, you see a chronological list of versions.
- Version creation
- A version is created only when a change is saved.
- Change information
- Each version has a time stamp and the details of what was changed.
- User attribution
- Each version identifies the user who saved the changes.
Versioning and execution history
When you select a specific version from the list, you can view the execution history that's associated with only that version. This helps you troubleshoot errors between versions such as identifying what specific change caused a flow to fail.
Flow restoration
When you revert to a previous version, Okta Workflows creates a duplicate of that flow. Intervening versions remain in the version history.
Considerations
Here are some important things to consider when using Workflows version history:
- Flow export
- Version history is local to the flow within its specific org. If you export or copy a flow, the version history isn't included. If you move a flow to a different folder in the same org, the version history is retained.
- Connections
- Reverting a flow restores the logic and card configurations, but it doesn't change the account connections that it used. Ensure that the required connections are active and authorized.
- Retention
- You can view up to 30 days of version history. Versions older than 30 days aren't retained.
Next steps