Skip to main content
Version: 1.28 (Current)

Stop Execution

Audience: Business Users

Skill Prerequisites: Actions, Conditions

Stops running actions. No further actions run, including the actions after any Execute Actions or Repeat that contains it, and no message is shown. Nothing that already happened is undone.

It's usually given a condition, so the rest of the actions only run when it makes sense.

Typical Use Cases​

  • Skip the rest of a submission when nothing has changed
  • End an On Error list so that nothing else runs after an error has been handled
  • Leave a Repeat loop and the remaining actions once a result has been found

Don't use it to​

Action NameDescription
Throw ExceptionStops with an error.
Display MessageShows a message and ends execution.
Execute ActionsGroups actions so one condition controls all of them.

Input Parameter Reference​

This action has no parameters. Use the action's Condition to control when it stops. See Common Parameters.

Considerations​

  • Stops everything. Nested lists don't limit it. It stops the list it's in, every list that contains it, and the actions after them.
  • Nothing is rolled back. Records saved, emails sent and files created by earlier actions stay as they are.
  • Final action. Actions placed after Stop Execution in the same list never run, unless its condition is false.

Examples​

tip

To understand how to use the below examples, please see Running Examples.

1. Stop when a request has already been processed​

This action stops all remaining actions when the Status token is Processed.

{
"Title": "Stop Execution",
"ActionType": "Result.StopExecution",
"Description": "Nothing to do for processed requests",
"Condition": "[Status] == \"Processed\"",
"Parameters": {}
}

Revised 09/25/2026