Error Messages

Overview

Error messages indicate a failure to load, save, or access content.

This page standardizes what evidence to capture and how to triage by category.

Key Concepts

• Error text: message shown in the UI
• Error code: numeric or short identifier when provided
• Timestamp: time of the error with time zone
• Scope: Account, Organization, Project, and page context

How It’s Used

Use this page when a reproducible error occurs and escalation is likely.

Use it to capture evidence that support can act on quickly.

Benefits

• Faster support triage
• Reduced repeated troubleshooting loops
• Better audit trail for production-impacting issues

Setup Steps

1

Capture the evidence set

Capture:

• exact error text (copy/paste)
• error code (if present)
• timestamp and time zone
• scope (Account, Organization, Project, page)
• screenshot with sensitive data redacted

2

Triage by category

Common categories include:

• Access errors: authentication or authorization failures
• Not found errors: item deleted, moved, or scope mismatch
• Timeouts: network delays or load issues
• Server errors: transient errors that may resolve after retry

If the category is unclear, escalate with captured evidence.

3

Apply a safe retry pattern

1. Refresh the page once.
2. Retry the action once.
3. Avoid repeated rapid retries to prevent rate limiting.

Best Practices

• Include at least one reproduction step sequence for support.
• Prefer permalinks to the affected item when available.
• Avoid sharing secrets in screenshots or recordings.

Summary

Error resolution is fastest when evidence includes text, timestamp, scope, and reproduction steps.