calendar_failed

A calendar provider refused the request or did not answer.

• Google Calendar, Microsoft Calendar or Calendly returned an error.
• The provider was unreachable or timed out.
• The calendar the booking targets was deleted or is no longer shared with the connected account.

• Retry with backoff — most provider faults are brief.
• If it persists, open the connection in the dashboard and confirm the target calendar still exists.

{
  "error": {
    "code": "calendar_failed",
    "message": "A calendar provider refused the request or did not answer",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/calendar_failed",
  "title": "Calendar Failed",
  "status": 502,
  "detail": "A calendar provider refused the request or did not answer",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• calendar_reauth_required
• upstream_error

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.