---
title: "Troubleshooting"
description: "Resolve Cadence MCP reachability, authorization, permission, conflict, and Inspector display errors."
canonical_url: https://cadence-me.com/developers/troubleshooting
last_updated: 2026-10-18
status: stable
source: src/data/developers.ts
---

# Troubleshooting

## Claude: Couldn't reach the MCP server

Confirm the exact endpoint ends in /mcp and is reachable by the client. The documented production URL is still pending hosted acceptance. A server with integrations disabled returns service_unavailable; changing client credentials cannot fix that.

Test discovery and OAuth with Inspector against the same configured endpoint. Use remote HTTP, not an invented SSE path. A browser GET to /mcp is not a connection test: authenticated GET returns 405. Check HTTPS, protocol negotiation, proxy headers and the Origin allowlist. Send only the error code and client version to [Support](/developers#support).

## Authorization fails

For invalid_grant, restart consent after checking the issuer, exact resource URL, redirect URI and PKCE verifier. Codes expire after ten minutes and can be used only once. Parallel refreshes can reuse an old token and revoke the family; serialize them.

If login loses the request, restart from the client in the same browser. Consent binds the signed-in account and browser request. A revoked connection needs a new consent; signing into the web app alone does not restore it.

## Read works but write fails

Check granted_scopes. Reconnect and approve the relevant write permission only if the user wants it. A client's cached tool list does not prove permission. For conflict, reread and compare the intended edit; do not remove the concurrency guard.

## Missing records or unexpected dates

Check the account timezone and local_date. Expand a bounded history window or follow next_cursor. Account-free desktop records are not hosted; linked changes must sync first. Needs decision is bounded in get_timeline. There is no automatic missed status.

## Inspector shows -32602 or schema warnings

Inspector 2.11.0 may validate error structuredContent against a success schema and display -32602. The server still returns isError and its stable code. Inspect the raw result or verify with an official SDK client. Nullable JSON Schema type arrays can also trigger Inspector portability warnings; do not rewrite the contract to silence them.

## Rate limits and uncertain edits

Wait for Retry-After or retry_after_seconds. For an uncertain write, reuse the original idempotency key and identical input within 24 hours. A new key can create a duplicate. See [safe retries](/developers/idempotency).

## ChatGPT account labels

Cadence omits the optional OpenAI profile marker to preserve the existing account-context schema. Account labels or duplicate-connection detection may be less reliable. Review the signed-in account on Cadence's consent screen.
