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-09-20 / 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 |
|---|---|---|
| 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 | Supply the user’s IANA zone |
| Previously working account fails | Provider consent or app password | Reconnect the existing account |
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.