Cancel the run and confirm its state
Use the cancellation action for the specific run you intend to stop, then refresh or wait for the run to report its status. A run may be running, waiting, succeeded, failed, or cancelled; confirming the final state prevents confusion about whether a cancellation request took effect.
If the workflow is waiting for a human response, cancellation can be appropriate when the decision is obsolete or the request was submitted in error. If it is still running, consider that a current step may be finishing while the run responds to the stop request. Avoid launching a duplicate run until you know what happened to the first one.
Account for steps that already completed
Inspect the recorded steps before cancelling or immediately afterward. A completed step may have sent a message, written data, or called an external service before the next step was stopped. Cancellation prevents future workflow progress; it is not a rollback of changes made by earlier steps.
If you still need the workflow, correct the cause and decide whether to retry the cancelled run or start a new one with clear input. Check the run history for attempts and outputs so a retry does not repeat an external action unintentionally. When the task is no longer valid, leave it cancelled and document why rather than resuming with placeholder data.