Yate has interactive and batch processing modes for action execution. There are four statements which control the ability to stop execution. Each of the statements can be executed always or only if the action test state is true or false.
This statement stops action execution. Note that if you are batch processing, execution will resume with the next process point of the batch processing sequencing. If you are in a Batch Start sub-action, control will resume with folder processing. If you are processing folders control will resume with the next folder containing audio files or the optional Batch End sub-action.
When batch processing, execution will resume with the next phase of the batch processing sequencing. If you are in a Batch Start sub-action, control will resume with folder processing. If you are processing folders control will resume with the optional Batch End sub-action. When executed in an interactive execution mode, the statement is equivalent to the Stop statement.
Regardless of the execution mode or where you are in a batch processing sequence, this statement stops all action execution. It is equivalent to hitting the Cancel button in the UI. Warning: modifications to open databases will not be saved when Cancel is executed.
This statement stops action processing and attempts to quit the application. Warning: All loaded files, hidden and visible, are closed without saving modifications. You will still be prompted if there are open databases with unsaved changes. The statement is not valid while batch processing.