Model Failure Modes in Business Workflows

Start here

Overview

Models fail differently than traditional bugs. This guide catalogs failure modes and mitigations for CRM-tied workflows.

Core concept

Definition

Failure modes include confident wrong extractions, misclassification under distribution shift, prompt injection via user content, and tool calls with plausible-but-wrong parameters.

Business impact

Why it matters

A single bad automated CRM update can propagate across teams. Design for graceful degradation.

Practical model

Framework

Confidence and checks

Validate formats, cross-check totals, require corroboration fields.

Human queues

Route low confidence to review—not auto-commit.

Implementation detail

Detailed breakdown

Monitoring

Track label distributions; alert on sudden shifts—possible drift or abuse.

In practice

Real-world example

A finance team blocked auto-posting when extraction confidence dropped after a vendor changed invoice layouts—triggering human review.

Avoid these

Common mistakes

Single-shot prompts for complex tables.
No kill switch during incidents.

Engineering layer

Technical patterns

Graceful degradation

If latency > SLO, skip LLM step and use rules-only path.
If confidence low, route to review queue with full context bundle.

Build patterns

Code examples

Circuit breaker around LLM

Opens after consecutive failures; uses heuristic path.

TypeScript

let failures = 0;
export async function callLlm(fn) {
  if (failures >= 5) return heuristicFallback();
  try {
    const out = await fn();
    failures = 0;
    return out;
  } catch (e) {
    failures++;
    throw e;
  }
}

System view

System architecture

YAML

[Workflow step: AI]
        → [Guardrails + timeout]
        → [Success path | fallback path]
        → [Metrics: failure reason codes]
        → [Human review on ambiguous]

Keep learning