non-interruptible-mode

Non-interruptible execution policies enforce finishing long-running task lists without interactive prompts or clarifications, reducing delays and context-switching. They apply to workflows such as batch processing, data pipelines, and automation scripts.

To stop a batch process from pausing, enable a non-interruptible execution mode that skips confirmations, avoids asking questions, makes reasonable assumptions, and selects a single approach to proceed through all tasks.

Yes, you can execute scripted automation tasks to completion by implementing a non-interruptible mode that skips clarification questions, makes reasonable assumptions, and proceeds through the entire task list without stopping.

Yes, non-interruptible execution still reports issues by collecting any concerns encountered during data pipeline workflows and reporting them only after all tasks are fully complete.

You should not use a non-interruptible policy for task execution when workflows require interactive human input, real-time clarifications, or critical decision-making before proceeding to the next step.