Repository navigation
Connecting a calendar fails silently when the provider refuses the calendar list #668
Description
Connecting a Google account can fail after consent with nothing shown and nothing logged. The callback exchanges the code, then lists the account's calendars. When that request gets a 403 (seen with a Workspace account whose consent included calendar.readonly), the callback redirects back with a 303, no connection is created, and the settings page shows the account list unchanged. The log has only httpx's status line, so the reason Google gave can't be seen.
Fix: log the provider's error code and message (no tokens or addresses), show the user why the connection failed, and check the Microsoft callback for the same gap.
Ours
Activity
Valtora commentedon Oct 23, 2026
Fixed by #669. The callback now lands on the Integrations page, where the Calendars card shows why connecting failed, and each failed step is logged with the provider's error code and message. The callback had been landing on a page that dropped its result since #154, so success never showed there either.
fix(calendar): log and show why connecting a calendar failed (Valtora…