Skip to main content

​
Resolving Errors

Manage the lifecycle of errors from discovery to resolution.

​
Error States

StateDescription
UnresolvedNew or recurring errors needing attention
ResolvedFixed errors, will reopen if they recur
IgnoredKnown issues you don’t want alerts for

​
Resolving Errors

​
In the Dashboard

  1. Click on an error
  2. Click “Resolve”
  3. Optionally add a note

​
Via API

curl -X POST https://reflex.brainzlab.ai/api/v1/errors/123/resolve \
  -H "Authorization: Bearer sk_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"note": "Fixed in commit abc123"}'

​
Via MCP

Ask Claude:
“Resolve the payment timeout error”

​
Auto-Reopen

When a resolved error occurs again:
  1. The error is marked Unresolved
  2. A notification is sent (if configured)
  3. The occurrence is linked to the original error
This helps you catch regressions.

​
Disable Auto-Reopen

For specific errors:
  1. Click on the error
  2. Click “Ignore” instead of “Resolve”
Ignored errors won’t reopen or send notifications.

​
Ignoring Errors

Ignore errors you know about but can’t or won’t fix:
  1. Click on an error
  2. Click “Ignore”
  3. Select duration:
    • Forever - Never alert
    • Until next release - Reopen on new commit
    • For 24 hours - Temporary ignore

​
Ignore by Pattern

Ignore all errors matching a pattern:
  1. Go to Settings > Ignore Rules
  2. Add a rule:
{
  "exception": "TimeoutError",
  "message": "*external API*",
  "environment": "staging"
}

​
Bulk Actions

Select multiple errors:
  1. Check the boxes next to errors
  2. Click “Bulk Actions”
  3. Choose: Resolve, Ignore, or Delete

​
Linking to Issues

Connect errors to your issue tracker:
  1. Click on an error
  2. Click “Create Issue” or “Link Issue”
  3. Choose GitHub, Jira, Linear, etc.
The error shows the linked issue status.

​
Resolution Notes

Add context when resolving: 
Fixed in PR #456
Root cause: Race condition in cache invalidation
Deployed: 2024-01-15
Notes are visible in the error timeline.

​
Error Timeline

Each error shows a history: 
Jan 15, 10:00  Created (first occurrence)
Jan 15, 10:05  +5 occurrences
Jan 15, 11:00  Assigned to @developer
Jan 15, 14:00  Resolved "Fixed in abc123"
Jan 16, 09:00  Reopened (new occurrence)
Jan 16, 10:00  Resolved "False positive, ignored"

​
Notifications on Resolution

Configure who gets notified:
  • Original assignee - Person who was assigned
  • Watchers - People following the error
  • Channel - Slack channel or email group

​
Metrics

Track resolution performance:
  • Mean Time to Resolution (MTTR) - Average time to resolve
  • Regression Rate - How often resolved errors reopen
  • Resolution by Team - Who’s fixing what
Access in Dashboard > Analytics > Resolution Metrics

​
Best Practices

​
Resolve with Context

Fixed in abc123

Root cause:
- Race condition when user clicked twice

Prevention:
- Added debounce to button
- Added idempotency key to API

​
Use Ignore Sparingly

Only ignore errors that are:
  • Known and acceptable
  • Out of your control (third-party issues)
  • Scheduled for future fix

​
Review Ignored Errors

Periodically review ignored errors:
  1. Go to Errors > Ignored
  2. Check if any should be fixed
  3. Delete obsolete ignores