How 10 enterprise systems deliver error messages—83 instances across 6 delivery mechanisms.
Get instant answers from our AI assistant. Trained on our research data from leading enterprise systems.
Error states use six primary delivery mechanisms: inline validation, toasts, modals, in-context messages, full-page errors, and banners. The choice of mechanism correlates strongly with error type—form validation is 90% inline, while 404s are 70% full-page.
Across 83 error instances from 10 enterprise systems, we found that inline validation (31%) and toasts (23%) dominate, together accounting for 54% of all error states. But frequency alone doesn't tell you which to use—context determines everything.
| Mechanism | Frequency | Primary Use Case |
|---|---|---|
| Inline validation | 31% (26) | Form errors, field-level validation |
| Toast | 23% (19) | System errors, transient failures |
| Modal | 13% (11) | Complex errors requiring action |
| In-context | 12% (10) | Contextual failures, loading errors |
| Full page | 10% (8) | 404s, critical failures, permissions |
| Banner | 10% (8) | Persistent issues, connection problems |
Frequency: 26 of 83 instances (31%)
Used by: All 10 systems
The dominant pattern for form-level errors. Message appears directly below or beside the problematic field, with the field itself highlighted (typically red border).
When it's used:
Visual components:
Recovery patterns:
| System | Style | Notable Pattern |
|---|---|---|
| Stripe | Red text, no icon | Shows specific product IDs and exact decline reasons |
| Linear | Red text below field | Includes exact dimensions for image errors |
| Airtable | Red text with icon | AI-powered "See suggestions to fix" for formulas |
| Notion | Red banner within modal | Uses for file size errors with upgrade CTA |
| GitHub | Pink/red text | Uses "can not" (two words) instead of "cannot" |
| Figma | Red text, polite | Uses "Please provide" pattern |
Frequency: 19 of 83 instances (23%)
Used by: 8 of 10 systems (not GitHub, not Airtable as primary)
Temporary notifications that appear at screen edge, typically auto-dismiss after 3-5 seconds. Used for system-level errors that don't require immediate action.
When it's used:
Visual components:
Recovery patterns:
| System | Position | Dismiss | Notable Pattern |
|---|---|---|---|
| Linear | Bottom-right | Yes | Shows exact dimensions for file errors |
| Figma | Top-center | No | Red/orange background, "An error occurred while..." |
| Slack | Top-center | Yes | Reassuring tone: "Sit tight while we reconnect" |
| Retool | Top-right | Yes | Developer-focused: exact JSON position errors |
| Atlassian | Bottom-left | Yes | "We" language: "We can't add Slack" |
| Notion | Bottom-left | No | Single use: file type not supported |
Frequency: 11 of 83 instances (13%)
Used by: 8 of 10 systems (not Linear, not GitHub)
Interrupting dialogs that require acknowledgment. Used for errors that need explanation or user decision.
When it's used:
Visual components:
Recovery patterns:
| System | Example | Words | Style |
|---|---|---|---|
| Slack | "File unsupported" | 2 | Terse, then detailed body |
| Airtable | "Can't import CSV file" | 4 | Contraction, specific |
| Asana | "Couldn't Upload File(s)" | 3 | Contraction, plural-aware |
| Atlassian | "We couldn't load your dashboard access settings" | 7 | "We" ownership, specific |
| Figma | "Imported to Drafts" | 3 | Status-focused (then shows failure) |
Frequency: 10 of 83 instances (12%)
Used by: 7 of 10 systems
Messages that appear within the content area where the error occurred, maintaining context. Common for permission and loading errors.
When it's used:
Visual components:
Recovery patterns:
| System | Style | Notable Pattern |
|---|---|---|
| Stripe | Minimal text | Exact card decline reasons for developers |
| Atlassian | Illustrated | Lock icon + detailed explanation + "ask a project admin" |
| Asana | Conversational | "Looks like you need access" + Request button with message field |
| Linear | Minimal | "Issue not found" — no illustration |
| Notion | Instructional | "Go online to edit this form" |
Locked sections: