Error Reference
Most TROPIKAL errors use a standard response shape with a short message. The table below explains what to check first.
HTTP status codes
| Code | Meaning | First check |
|---|---|---|
| 400 | Bad request | Required field missing, invalid JSON, or unsupported value. |
| 401 | Unauthorized | The session or API key is missing, expired, or invalid. |
| 403 | Forbidden | The account, plan, or website permission does not allow the action. |
| 404 | Not found | The resource does not exist or does not belong to the current account. |
| 409 | Conflict | A unique value already exists or the resource is in the wrong state for the requested action. |
| 422 | Validation failed | The submitted fields do not match the resource schema. |
| 429 | Rate limited | Too many requests or the account has reached a usage limit. |
| 500 | Server error | Retry later and include the request details when contacting support. |
Job errors
| Symptom | Check |
|---|---|
| Job not found | Confirm the job slug and that you are signed in to the owning account. |
| Chat rejected | Confirm the job is active and the request uses the expected auth method. |
| Capability call failed | Check the linked function, required fields, and capability-specific permission. |
| Connected account needs reconnect | Open Accesses, reconnect the account, then rerun the job. |
| Knowledge answer missing | Confirm the knowledge source is processed and active for that job. |
| Website publish destination missing | Confirm the website is connected, validated, and synced with a publish action. |
| Review required before publish | Complete the review step before the job sends content to the website. |
Website connection errors
| Symptom | Check |
|---|---|
| Validate required | Open the website connection and click Validate. |
| Connection not ready | Read the failed readiness check and retry after the website is corrected. |
| Sync failed | Retry Sync Connected Data after the connection is ready. |
| Publish action missing | The website is connected, but no publish action is available. |
| Action denied | Use a lower-risk action or ask TROPIKAL support to review the Connected Data access. |
Calendar booking errors
| Symptom | Check |
|---|---|
| Available times cannot load | Confirm the website is connected and the selected Google Calendar Access does not need reconnection. |
| Booking setup cannot finish | Reconnect Google Calendar, approve availability and event access, then run the booking calendar setup again. |
| No open dates appear | Check the Job’s Booking schedule, closed dates, booking horizon, and busy calendar events. |
| Selected time is unavailable | The calendar changed after the slot was shown. Refresh and choose another returned time. |
| Human check rejected | Refresh the page, complete the new check, and retry the same slot. |
| Calendar invitation missing | Confirm the attendee email and check the created Google Calendar event. Booking delivery uses the Calendar invitation. |
See Website Calendar Booking for the complete owner setup and verification flow.
External MCP client errors
This section is for developer tools such as ChatGPT MCP connections. Website dashboard setup should use Website quickstart.
| Symptom | Check |
|---|---|
| Client says MCP does not implement OAuth | Confirm the MCP server URL is exactly https://mcp.tropikal.ai/mcp, then remove and re-add the connection. |
Direct request says Bearer token required |
This usually means the request was not authorized. Use the client connection flow instead of opening the endpoint directly. |
| Action denied | Confirm the account and approved access allow the requested read, write, publish, or destructive action. |
What to include when reporting an issue
Include:
- Product area: Jobs, Websites, or API.
- The page or action you were using.
- The visible error message.
- The approximate time of the request.
- The job slug or website name, if relevant.
Do not include passwords, API keys, setup codes, browser cookies, or private credentials in support messages.