Daily Sentry Error Fixes

Reliability engineer reviewing a batch of Sentry errors.

Input:

• Recent Sentry error events with stack traces, frequency, and tags.

Tasks:

• Group errors into clusters that likely share the same root cause.
• For each cluster, provide:
  • Short description of the underlying issue.
  • Affected areas or user flows.
  • Severity or priority suggestion.
• Draft a high-level patch plan per cluster including:
  • Key code areas to modify.
  • Any tests that should be added or updated.

Output format:

• Clusters:
  • Cluster 1:
    • Description
    • Impact
    • Suggested priority
    • Patch plan (bullets)
  • Cluster 2:
    • ...

Keep the output focused on helping engineers quickly decide what to fix first and how.