A new Sentry error has been detected. Use the Sentry MCP to investigate and resolve the issue. **Step 1: Gather Issue Details** Use Sentry MCP tools to gather comprehensive information about the issue: - Get full issue details including stack trace, error message, and context - Review the URL and environment where the issue occurred - Check issue metadata (priority, frequency, affected users) - Search for related errors in the same files or project **Step 2: Determine Actionability** Carefully analyze the issue details to determine if there is anything actionable to fix: - Review the stack trace for clear error causes - Check if the error is reproducible and has sufficient context - Consider the frequency and impact of the issue - If the issue is unclear, lacks context, or requires further investigation, do not proceed. Instead, give investigation steps and stop here **Step 3: Handle Source Maps** If the stack trace from Sentry is minified, this indicates that source maps are not properly configured. In this case you should not attempt to solve the issue. Instead, you should set up proper source map uploads so that future issues can be resolved. In that case, explain to the user why you are doing that and what additional environment variables / CI setup they might need to complete. **Step 4: Implement Fix** If there is something actionable (based on your analysis): - Focus on fixing the immediate issue identified - Use the stack trace and error context to guide your solution - Avoid overdoing it with error handling, cleaning up other problems, etc. - Avoid making breaking changes - Avoid silencing important errors as a solution Ensure the solution is robust and follows best practices. Add tests to validate the main logic, avoid adding excessive or redundant tests. **Step 5: Create Draft Pull Request** Create a draft pull request with the following structure: --- **PR Title:** [Sentry] <brief description of error solved> ## Issue Analysis **Error Type:** `<error type/exception>` **Summary:** <Two sentence summary of what caused the issue and how it was fixed> ## Issue Metadata - **Priority:** <priority> - **First Seen:** <firstSeen> - **Last Seen:** <lastSeen> - **Event Count:** <count> ## Links - **Sentry Issue:** [<shortId>](<permalink>) ## Additional Context <details> <summary>Sentry Issue Details</summary> ```json <Complete issue details from Sentry MCP> ``` </details> <details> <summary>Webhook Payload</summary> ```json <Complete webhook payload> ``` </details> --- **Note for AI:** - DO NOT use the `{fixes,resolves,addressed} <SENTRY_ISSUE_ID>` syntax in your commit message or pull request description to mark the issue as resolved - Use Sentry MCP tools to gather all necessary context before implementing a fix - Pay special attention to the stack trace, error message, and reproduction context - URL encode the follow-up prompts in the query parameter - Replace `<agent-session-id>` with the actual agent session ID --- Below is the webhook payload from the Sentry event: