Migrate and change running instances

Move running instances to a newer flow version, move a token to another element, and edit an instance's variables, with a preview and a reason for every change.

A running instance stays on the version it started with. When you publish a fix or an improvement, you can migrate instances that are already running to the new version. You can also move a token by hand or change variables. All three are override commands: they need pulse.override, ask for a Reason of at least 10 characters, and are audited with the state before and after. Migrate an instance to another version# Before you start, publish the target version of the same flow. See Publish a new version. In Flow Monitor, open the running instance. Select Migrate. Choose the Target version. A dry run fills the Element mapping: Source element and Target element: elements are matched by their id, so an element you kept in the new version maps to itself. Unmatched means the target has no element with that id. Token: Moves for each element that holds a token now, or Blocked with the reason. Enter a Reason and select Migrate instance. The instance is now pinned to the new version and continues from the same place, under the new version's rules: A migration is refused when: a token is inside a multi-instance activity, or would change scope (for example move into or out of a sub-process); a waiting token would map to another kind of element (a user task to a robot task, for example); an element, or an event the instance listens to, is missing from the target; the target version cannot run. To migrate many instances, select them on the Instances tab and choose Migrate. The dry run shows how many are affected and refused, grouped by reason. See Run a bulk operation. Keep element ids stableMigration maps elements by id. When you change a flow that has running instances, keep the ids of the elements you keep, and add new elements rather than renaming or retyping existing ones. Move a token# Use Move token to skip a step or send an instance back to an earlier one. Open the running instance and select Move token. Under Cancel the token on, tick the elements whose tokens to cancel. Under Start a token on, choose the element where the instance continues. Check Before and After, enter a Reason and select Move token. If a cancelled token still has a running job or an open Action Hub task, the dialog lists it under Cancel these first, with a link. Cancel the job or task, then move the token. Edit variables# You can change an instance's variables while it is suspended or stopped at an incident, for example to correct a value before you retry. Open the instance and select Variables ▸ Edit variables. Change the JSON under Variables. The Preview lists each Variable with its value Before and After. Enter a Reason and select Save variables. To change variables and run a failed step again in one go, use Retry with variable edits on a The job failed incident. See Resolve incidents. Next steps# Monitor flows Audit log

Migrate an instance to another version

Move a token

Edit variables

Next steps