AI-Adjacent Issue
Tool Failure Escalates Into Policy Decision
A tool, connector, API, or integration failure is treated as a policy, safety, approval, or governance decision instead of a runtime failure.
What This Looks Like
A tool, connector, API, integration, or runtime call fails, but the system treats the failure like a policy decision, safety block, approval result, compliance issue, or governance outcome. A technical failure may become a refusal, escalation, risk label, or policy-style answer.
Why Users Blame AI
The user sees the final AI behavior, not the low-level tool failure. The response may look like the AI decided something was not allowed, unsafe, noncompliant, or unapproved, when the original cause was a runtime, connector, schema, permission, or availability failure.
What to Check First
- Whether a tool, API, connector, or runtime error occurred first
- Whether the failure was converted into a policy-style message
- Whether the workflow distinguishes runtime failure from governance decision
- Whether retry or fallback behavior exists for tool failure
- Whether escalation rules treat missing tool data as risk
- Whether human review sees the actual failure cause
When This Is AI-Adjacent
Use this AI-Adjacent Issue when a technical tool failure is elevated into a policy or governance decision. If the risk signal escalates beyond evidence, use the related Workbench Issue. If human and automated review disagree after the failure, use the related review-disagreement Issue.
Related Workbench Issues
Risk Signal Escalates Beyond Evidence
A risk signal, warning, score, or concern escalates farther than the available evidence supports.
Small Issue Keeps Escalating
A small issue, warning, uncertainty, or correction keeps increasing in severity, scope, or workflow impact across later steps.
Model Output Triggers Unapproved Action
AI output causes, recommends, or triggers an action that has not passed the required approval, permission, or authority check.
Human Review and Automation Disagree
A human review result and an automated AI or workflow result disagree without a declared rule for resolving the difference.
Same Case Has Conflicting Policies
The same case appears to be governed by multiple policies, rules, or standards that point to incompatible outcomes.
Common Ways People Describe This
- tool failure escalates into policy decision
- AI tool error became policy refusal
- connector failure treated as safety issue
- API failure escalated to governance decision
- tool outage caused policy block
- runtime failure became approval issue