Flows

Flow versioning and publishing

Flows support versioning so you can safely test changes without affecting production deployments.

How versioning works

When you edit a Flow, you’re working on a draft. Save your changes with the Save button. Saving does not affect Products using the Flow until you publish.

Publishing creates an immutable version that Products reference. Further edits create a new draft.

Publishing a Flow

  1. Make your changes and click Save
  2. Test the Flow to verify it works
  3. Click the chevron next to Save and choose Publish (or Save & Publish if you still have unsaved changes)
  4. Confirm to promote this draft to the live version

Products using this Flow will now use the latest published version.

Version numbers

Runtype automatically assigns version numbers:

  • v1 — First published version
  • v2 — Second published version
  • v3 — And so on

Version notes help you remember what changed in each version.

Draft vs published

DraftPublished
EditableImmutable
Not used by ProductsUsed by Products
Can be discardedPermanent
Only you see changesAll users see changes

Testing before publishing

Always test drafts thoroughly:

  1. Run the Flow with representative inputs
  2. Check all conditional branches
  3. Verify outputs are correct
  4. Test error cases
  5. Review execution logs

Only publish when confident the Flow works as expected.

Publishing immediately updates all Products using this Flow. Test thoroughly before publishing to avoid breaking production surfaces.

Viewing version history

  1. Open the Flow
  2. Click Versions
  3. See all published versions with timestamps and notes

Loading a previous version

If a new version causes issues:

  1. Go to Versions
  2. Find the previous working version
  3. Click Load to load that version’s steps into the editor
  4. Publish the loaded version

This creates a new version with the same steps as the old one. The problematic version remains in history but is no longer the published version.

Note: Loading a previous version will discard any unsaved changes in the editor.

Best practices

  • Publish frequently: Small, incremental changes are safer than big releases
  • Write version notes: Document what changed for future reference
  • Test before publishing: Always verify changes work correctly
  • Use development Products: Test Flows in a dev Product before adding to production
  • Monitor after publishing: Check execution logs for errors after deploying changes

Next steps