Stop, Continue, or Ignore are the three common outcomes used to control how a workflow reacts to a failed custom step. Stop halts the run immediately, Continue proceeds but marks the run failed at the end, and Ignore proceeds while treating the overall run as successful.
What the outcomes mean for workflow control
Stop, Continue, or Ignore define the execution policy a workflow uses when a custom step fails. The choice determines whether the run aborts immediately, finishes with a failure state, or keeps moving and reports success, so the setting is less about formatting and more about how the automation platform handles exceptions.
Stop is the safest default when a failed step could leave partial changes, inconsistent state, or uncertain downstream assumptions. It prevents the workflow from compounding an error by continuing with invalid inputs or an incomplete prerequisite.
Why the outcome choice matters operationally
Continue is useful when the failed step is important but not essential to the rest of the workflow, such as a non-critical notification, enrichment task, or reporting action. The run still records failure, which preserves visibility without forcing an immediate stop.
Ignore is the most permissive option. It keeps the workflow moving and treats the overall run as successful, which can be appropriate only when the failed step is truly optional and its failure does not change the meaning of the run.
The practical difference between these outcomes is how much failure the process is allowed to tolerate. In an automation chain, that tolerance affects reliability, auditability, and the confidence operators can place in the final result.
Where each setting fits in a workflow
Use Stop when the failed custom step is a gate for later actions, especially if later steps depend on data it produces or validation it performs. A stopped run makes the failure explicit and avoids giving downstream steps a false sense of completion.
Use Continue when you want the workflow to complete but still surface that something went wrong. This is often the best fit for auxiliary steps where the business process should keep going, yet the failure still needs review.
Use Ignore only when the step is genuinely optional and the workflow should be considered successful even if that step fails. That makes it a design choice about acceptable loss of function, not a convenience setting for hiding errors.
Failure handling and reporting implications
The choice also changes how operators interpret automation health. A Stop outcome usually signals a hard dependency failure, while Continue and Ignore can make a run appear more resilient even when one or more steps did not succeed.
That means teams need to be clear about what “success” means for the workflow as a whole. If a failure is ignored in a place that really matters, the run result may be technically successful while the underlying business action is incomplete or misleading.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Workflow failure handling is part of resilient operational configuration. |
| Recommendation — Define workflow failure behavior so critical steps stop on error and noncritical steps are explicitly tolerated. | ||
| NIST CSF 2.0 | PR.IR-01 — Networks and environments are protected and resilient | Outcome settings influence recovery behavior and operational resilience in automated workflows. |
| Recommendation — Set workflow error-handling rules that preserve resilience when steps fail. | ||
| NIST SP 800-53 Rev 5 | SI-4 — System Monitoring | Failure outcomes affect how automation errors are surfaced for monitoring and response. |
| Recommendation — Monitor workflow failures and treat suppressed errors as events that still need review. | ||
| ISO/IEC 27001:2022 | A.8.9 — Configuration management | The setting is a workflow configuration decision that should be governed consistently. |
| Recommendation — Control workflow failure settings through approved configuration management. | ||
Related resources from NHI Mgmt Group
- What breaks when fraud controls stop at onboarding and ignore payout time?
- What breaks when fraud controls stop at checkout and ignore returns or refund abuse?
- What breaks when identity controls stop at the endpoint and ignore the browser session?
- When should teams stop an agentic workflow instead of letting it continue?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org