Sentry API token expired - Scanner failing

[claude]

Issue

The automated Sentry scanner is failing due to an expired API token.

Error: {"detail":"Token expired"}

Impact:

• No proactive Sentry issue monitoring
• New errors/performance regressions not being auto-tracked
• GitHub issue automation pipeline broken

Fix Required

Update the SENTRY_API_TOKEN environment variable in GitHub Actions secrets:

1. Go to https://sentry.tryethernal.com/settings/account/api/auth-tokens/
2. Create a new token with project:read permissions
3. Update the secret in GitHub repository settings under Actions secrets

Verification

Once fixed, the next scheduled Sentry scanner run should succeed and show:

=== Sentry Scanner Summary ===
Status: SUCCESS
Errors scanned: X
Performance issues scanned: Y

---

Created by Sentry Scanner

[claude]

Escalating: This is an infrastructure/config problem that requires manual intervention. The fix requires:

1. Accessing Sentry account settings to create a new API token
2. Updating GitHub repository secrets with the new token

This cannot be automated through code changes and needs human access to external services. @antoinedc please review.

[claude]

Status Update - 2026-04-10 01:33:40 UTC

The Sentry scanner attempted to run and confirmed the token is still expired.

Current Error: {"detail":"Token expired"}

Attempted Operations:

• ❌ Backend errors (ethernal-backend): Failed to fetch
• ❌ Backend performance (ethernal-backend): Failed to fetch
• ❌ Backend regressions (ethernal-backend): Failed to fetch
• ❌ Frontend errors (ethernal-frontend): Failed to fetch
• ❌ Frontend performance (ethernal-frontend): Failed to fetch
• ❌ Frontend regressions (ethernal-frontend): Failed to fetch

Scanner Activity Analysis:
Recent scanner effectiveness (before token expiration):

• Total sentry issues tracked: 200+
• Issue types created: Incidents, regressions, performance, errors
• Last successful runs: April 3-4, 2026
• Most common findings: N+1 queries, connection timeouts, database deadlocks

Recent Issue Pattern Analysis:

SequelizeConnectionError regressions: 3 issues  
Performance regressions (N+1 queries): 6 issues
Database incidents (deadlocks): 2 incidents
RPC timeout incidents: 1 incident

The scanner has been highly effective at catching regressions and performance issues when working. Immediate token renewal recommended to restore monitoring coverage.