You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Calendar sync retries a revoked Google token forever instead of asking to reconnect #661
When Google refuses a refresh token, its token endpoint answers 400 with error: invalid_grant and a description such as "Bad Request". _extract_error_text_from_payload (backend/services/calendar_service/text_utils.py) keeps only the description, so _classify_sync_failure never sees invalid_grant and marks the account "Needs attention" instead of "Reconnect required". The 15-minute sync and the push sweep then retry the refresh indefinitely, about ten token requests an hour per account. Settings shows only "Bad Request", and the dashboard keeps showing the calendar as it was at the last good sync.
Fix: classify token-endpoint failures on the OAuth error code (invalid_grant, interaction_required, consent_required, login_required, Microsoft's AADSTS invalid_grant included), and keep reconnect-required accounts out of the push sweep and the reconcile after a sync.
Fixed by #667. A refused grant is now read from the OAuth error code and marks the account Reconnect required, and such accounts stop requesting tokens and leave the push sweep until they reconnect.
Activity
Valtora commentedon Oct 23, 2026
Fixed by #667. A refused grant is now read from the OAuth error code and marks the account Reconnect required, and such accounts stop requesting tokens and leave the push sweep until they reconnect.
fix(calendar): stop retrying refused grants and failed push channels (V…