Error Messages in Tabidoo
When working with Tabidoo (both in the UI and via API), users may encounter various error messages. These messages usually follow standard HTTP status codes and indicate where the problem occurred. This document explains the most common error categories, their meaning, and how to resolve them.
Where to find the details
- In the application – the message on the screen. Copy its full text before you close it.
- In a workflow – open the workflow and check its run log (the newest run first). If the System Log extension is installed, errors are also written there.
- In an integration – the HTTP status code and the error message in the response body.
- For limits – click your avatar → Data usage. It shows which limit you are close to and what used it.
Errors caused by limits
| What happens | Cause | What to do |
|---|---|---|
| You cannot create another application, table, or field | Plan limit reached (stopped at 150 %) | Upgrade, or delete what you no longer need |
| New records cannot be added | Records per application reached (stopped at 150 %) | Upgrade, or delete old records |
| No data can be saved in an application at all | The application has been over its limit for more than 35 days | Upgrade, or delete records or tables |
| A file is refused | The file is over 50 MB, the record already has 1,000 attachments, or storage for attachments is full | Split or compress the file, clean up old attachments |
| An integration or a workflow cannot load data until the next day | Loaded data per day | Wait for the next day; then load only what changed and filter on the server – see Limits in Tabidoo |
| Attachments cannot be downloaded until the next day | Loaded attachments per day | Wait for the next day, download fewer files |
| Workflows stop running | Workflow runs, Workflow time, or Long-running workflow time per day | Check Data usage, find the workflow that used the most |
| The AI does not answer | Free AI credits for the month are used up | Buy credits or upgrade |
| A request asks for too many records | One request asked for more records than your plan allows; the message tells you the maximum | Ask for fewer records and page through the rest |
| An Excel import is refused | The file is over 100 MB, or has over 10,000 columns or 400,000 rows in a sheet | Split the file |
| E-mails from workflows arrive late | The application sent more than 100 e-mails in a minute or 1,000 in an hour – the rest is sent later | Send fewer e-mails at once, for example one summary e-mail instead of one per record |
| The application is temporarily locked | Maintenance of the application is in progress (at most 2 hours) | Wait and try again later |
| A warning says the record history (audit) is over its limit | The record history of the application is over 2× its record limit | See Data audit limitation |
For all limits and their values, see Limits in Tabidoo.
Workflow errors
| Message | What it means | What to do |
|---|---|---|
| Javascript was terminated after 90 sec. timeout | One run of the workflow took longer than 90 seconds | See the article |
| Circular workflow call detected | Workflows keep starting each other – more than 5 runs for one record, or more than 50 in one chain | Add conditions to the triggers, for example run only when a specific field changes |
| Unhandled rejection in the log | A script did not wait for a call with await | Add await before every doo.table, doo.functions, and doo.ai call |
A webhook answers HTTP 200 even when the workflow script fails. If a webhook "succeeds" but nothing happens, check the run log of the workflow.
See also Behavior of Workflow.
HTTP status codes (API, integrations, MCP)
| Code | Meaning | Common causes | What to do |
|---|---|---|---|
| 400 – Bad Request | The request is invalid | A required field is missing, invalid JSON, a value in a wrong format (for example a dropdown value that is not one of its options) | Check the API documentation and the field formats |
| 401 – Unauthorized | You are not signed in | An invalid or expired API token | Check the token, create a new one if needed |
| 403 – Forbidden | You are signed in, but not allowed | Your role does not allow the operation; for MCP, the application may have Restrict AI/MCP to read-only access turned on | Check the role, or ask the application owner |
| 404 – Not Found | The object does not exist | A wrong URL, record ID, or a deleted object | Check the URL and the ID |
| 429 – Too Many Requests | Rate limit reached | Too many requests per minute or per hour | Wait at least a minute, then add pauses or use bulk operations. Data usage shows them as Rejected requests (429). |
| 500 – Internal Server Error | Unexpected error on our side | – | Try again after a short while. If it keeps happening, contact support. |
| 502 – Bad Gateway | Temporary communication error | – | Try again |
| 503 – Service Unavailable | The server is overloaded or under maintenance | – | Try again later |
| 504 – Gateway Timeout | The server took too long to answer | A large request or a slow workflow | Ask for less data at once, page through records |
Handling errors in an integration
- Retry only temporary errors – 429, 500, 502, 503, and 504. Wait before each retry and make the pause longer every time (for example 1 minute, 2 minutes, 4 minutes).
- Do not retry 400, 401, 403, or 404 without changing the request – the same request fails again and only uses up your rate limit.
- Log the whole response, not only the status code. The message in the response body usually says exactly what is wrong.
When you contact support
Send us the following to support@tabidoo.cloud – it saves a round of questions:
- the exact text of the message (or a screenshot),
- the time when it happened,
- the application and table,
- what you were doing (a save, an import, a workflow, an API call).