ข้ามไปยังเนื้อหา
การนำทางเอกสาร

เริ่มที่นี่

ผลิตภัณฑ์

การเชื่อมต่อ

SDK

MCP

MCP troubleshooting

Sign-in and roles

HTTP 401 means missing or invalid bearer credentials, an expired or revoked grant, wrong resource, or lost membership/owner-admin role. Sign in again with an organisation owner or admin account. A member role is insufficient. Authorisation is rechecked on every request. Only the workspace owner can use add_comment, even with a write scope.

Billing required

HTTP 402 means the organisation workspace needs active billing. Recover billing in Upweight; repeated token changes will not fix this. See billing.

Missing permissions

HTTP 403 with insufficient_scope means the token lacks the required tool scope. Review the requested permissions and reconnect with appropriate consent. Write scopes do not imply read scopes. A 403 can also be an Origin mismatch, not a scope problem. See the tool reference.

Client compatibility

Check client requirements and protocol versions. GET/DELETE return 405: use stateless POST, not SSE. Modern header and body metadata must agree. A transport or version mismatch can return HTTP 400 with JSON-RPC errors. Generic MCP support does not prove CIMD support; do not substitute a client secret or static token.

Organisation selection

Check the workspace shown during browser consent before approving. Consent currently resolves the organisation from your most recently added membership; it does not offer an organisation selector or accept an organisation override. Do not assume a different app selection changes the OAuth target. Each grant is bound to one organisation; it does not grant access to every organisation you belong to. Use get_workspace to verify the connection target.

Disconnect an app

Account settings combines active scopes across organisations for each client; this display is not a single cross-organisation grant. Disconnect revokes all of this user's grants for that client across all organisations, including access and refresh grants. It never revokes other users' grants. The next call must authenticate again. “Last renewed” refers to refresh issuance, not last use.

Rate limits

HTTP 429 includes a Retry-After header in seconds. Wait for that interval rather than retrying immediately. MCP requests are limited to 120 per minute per access token and 300 per minute per IP. Reconnect only for an authentication issue, not to evade a limit.

ตรวจสอบล่าสุด