Page unavailable? Copy its Markdown and paste it into your chat.
An assistant cannot access a calendar
Distinguish cached tools, missing scopes, excluded calendars and expired connections.
Reviewed · 2026-10-13 / Ridian
Find the actual failure
Section titled “Find the actual failure”First determine whether the client attempted a tool call. A conversational refusal, a missing tool and a server response are different evidence. Record the tool name, approximate time, request ID if provided, and a redacted error.
| Symptom | Check | Next step |
|---|---|---|
| Registration succeeded but the assistant is not connected | Check whether you returned to the assistant approval or only opened the Ridian dashboard | Start Connect again in the assistant; signing up and connecting a calendar alone do not complete assistant approval |
| Create tool absent | Client’s tool list and write scope | Refresh connector; if needed reconnect and start a new chat |
| Calendar absent | Workspace, ownership, provider status, calendar selection | Correct the intended selection without granting unrelated accounts |
| Read works, write fails | Provider read-only flag, event type, client write permission | Use an allowed standalone test event |
| CalDAV asks for a zone | Calendar has no usable timezone metadata | In Alvin, check the saved timezone and profile read permission; for external MCP calls, supply the IANA zone |
| Previously working account fails | Provider consent or app password | Reconnect the existing account |
| Mailbox permissions are greyed out under AI & Assistants | The assistant was connected before it requested mailbox access | Disconnect Ridian in the assistant and connect it again |
| Search interval is rejected | More than 744 elapsed hours, such as 31 days across the end of daylight saving time | Shorten or split the period into consecutive windows; a range limit does not require reconnecting the account |
Confirming your email
Section titled “Confirming your email”When you sign up from an assistant, the email contains only a six-digit code; enter it in the window where you signed up. If that window is gone, sign in with the same account: Ridian sends a new code and shows where to enter it. After a link from a regular sign-up, wait for sign-in to finish, then select Continue. If you see Sign in to continue, sign in with the same account. If the original assistant request has expired or you land on the dashboard, start Connect in the assistant again.
On the plan selection screen, choose Continue with Free to finish setup without buying a plan. Free plan limits still apply.
Continue expired setup
Section titled “Continue expired setup”Your connected accounts remain saved. Choose Open connection guide, then start a fresh connection from your assistant. Sign in with the same Ridian account and workspace. After connecting, copy an example prompt such as “What’s my next meeting?” and paste it into your assistant.
Under Need help getting started?, you can email Paul or book 30 minutes to work through setup together.
Do not diagnose from wording alone
Section titled “Do not diagnose from wording alone”The assistant may describe a missing tool as a permission issue. Conversely, a refreshed tool list does not override a real authorization failure. Compare the client’s observation with the connection state in Ridian.
Escalate with minimal evidence
Section titled “Escalate with minimal evidence”Send support the client, provider, failed operation, time and request ID. Remove event contents, attendee addresses, private feed URLs and tokens. A screenshot of the permission settings with sensitive fields redacted is more useful than copying a whole private conversation.