Adding Steps to a Run in progress
Sometimes a particular run needs a step the workflow does not have. You can add it to that run alone, without changing the workflow or any other run.
Add a step to one run
Open the run, use the More menu at the top right, and choose to add steps. You can add steps there and remove them, and the changes stay inside this run.
This has to be enabled for the workflow first. See How to add ad hoc steps to a workflow run.
The consequence worth knowing
Customizing a run stops it following the workflow, permanently. Once you add a step directly to a run, that run will never again appear in the list of runs eligible to receive workflow updates, even after the step is removed.
That is deliberate: the run now contains a decision somebody made for this specific piece of work, and pushing the workflow over it would throw that away. But it does mean a run you tweaked once can no longer be brought back into line automatically.
Which to choose
- The step belongs in this run only, because of something particular about this customer or site: add it to the run.
- The step was missing from the process and should have been there all along: fix the workflow instead and push the change out to runs in progress. See Updating Runs When a Workflow Changes.
The second is the one people get wrong. If you find yourself adding the same step by hand to run after run, it belongs in the workflow.