Issue Boundary
AI-Adjacent Issues
Problems users may experience as AI failures, but which may involve tools, apps, permissions, runtime behavior, configuration, product surfaces, or integrations.
Agent Keeps Adding Tool Dependencies
An agent keeps adding required tools, connectors, searches, files, APIs, or integrations instead of completing the task with the available surface.
Agent Uses Old Tool Schema
An agent, prompt, workflow, or integration continues using an older tool schema after the tool contract has changed.
AI Works in One Environment Not Another
The same AI task appears to work in one app, mode, model, account, workspace, or runtime but fails or behaves differently in another.
Category Has Too Few Issues to Be Useful
A category, diagnostic area, or intake bucket has too few Issues, examples, or checks to support useful diagnosis or routing.
Documented Field Not Available at Runtime
A documented field, option, parameter, property, or capability is expected by the user or agent but is not available in the actual runtime.
Generated Output Changed Hidden Metadata
Generated output changes hidden metadata, identifiers, references, state, or system fields that affect later behavior but are not obvious in the visible output.
Guardrail Applies to One Model Path Only
A guardrail, policy, validation rule, safety check, or workflow constraint applies to one model path, mode, runtime, or route but not another.
Low-Level Configuration Overrides Workflow Policy
A low-level configuration, product setting, connector rule, runtime option, or environment flag overrides the workflow policy the user expects to govern the task.
One Workspace Affects Another
State, memory, files, permissions, settings, tools, or workflow effects from one workspace affect another workspace where they should not apply.
Permission Change Not Applied
A permission, approval, role, policy, or access change is made but the AI, agent, tool, or workflow continues behaving as if the old permission state still applies.
Runtime Behavior Does Not Match Docs
Documented behavior, fields, tool schemas, permissions, or runtime capabilities do not match what actually happens during use.
Too Many Workflows Depend on One Tool
Many workflows, agents, checks, or downstream paths depend on one tool, connector, API, or integration, creating a shared point of failure.
Tool Call Caused Hidden Downstream Change
A tool call causes a downstream state, workflow, metadata, record, or integration change that is not visible at the point of action.
Tool Effect Crosses Target Boundary
A tool, connector, function, or integration affects an object, file, record, workspace, or state surface beyond the intended target.
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.
Tool Not Supported in This Mode
A tool or capability appears unavailable in the current mode, environment, product surface, or runtime context.