Limits in Tabidoo

Tabidoo runs on shared infrastructure, so every account works within limits. They keep the platform stable for everyone and let you start small and grow with a bigger plan.

Where to see your consumption: click your avatar in the top right corner and open Data usage. The Consumption tab shows every limit, how much of it you have used, and what used it. On the Notifications tab, you can get an alert before you reach a limit. See Data Usage.

There are four kinds of limits:

Kind	What it answers	How it behaves
Plan limits	How much can I build and store?	Checked when you create or save something
Daily and monthly limits	How much work can my account do?	Counted per day (AI credits per month), reset automatically
Rate limits	How many requests can I send per minute?	Slow you down first, then reject
Technical limits	How big can one file, run or import be?	The same for every plan

Plan limits

	Free	Basic	Standard	Pro	Individual
Applications	2	10	25	100	Unlimited
Tables per application	10	25	50	250	Unlimited
Records per application	500	25,000	50,000	250,000	Unlimited
Storage for record data	100 MB in total	3 GB	5 GB	25 GB	As agreed
Storage for attachments	(included above)	7 GB	95 GB	975 GB	As agreed
Workflow runs per day	20	1,000	5,000	10,000	Unlimited
Workflow time per day	10 min	30 min	30 min	30 min	Unlimited
Long-running workflow time per day	–	–	–	30 min	Unlimited
Free AI credits per month	1 €	5 €	10 €	25 €	As agreed
Record history	2 weeks	3 months	Unlimited*	Unlimited*	Unlimited*

On paid plans, storage for record data and storage for attachments are counted separately – filling one does not affect the other. On the Free plan, they share 100 MB.

* When the record history of an application grows over 2× its record limit, Tabidoo shows a warning. See Data audit limitation for what to do.

Values change over time. The pricing page is always the authoritative source, and Data usage shows the exact limits of your account.

Daily and monthly limits

These limits are not about how much you have built, but about how much your account does. You see all of them in Data usage → Consumption.

Limit (as shown in Data usage)	What it measures	Period
Workflow runs	Runs of server workflows	day
Workflow time	How long server workflows ran	day
Long-running workflow time	How long long-running workflows ran – workflows for which you set a longer run time (Pro plan and higher)	day
Loaded data	Data loaded from the database by the API, workflows, MCP, and system recalculations after a record change	day
Loaded attachments	Attachments downloaded by users, the API, and workflows	day
Free AI credits	AI credits spent from the free monthly credits of your plan	month

Daily limits reset every day at midnight UTC.

These counters belong to the application owner, not to each user. If several people work in your applications, their activity adds up into one shared budget. All your applications share it too.

Below the limits, Data usage also shows statistics without a limit, such as public API requests, MCP calls, or e-mail recipients. They help you see where your usage comes from.

For developers: a script can read the same values with doo.environment.getCurrentUserTechnicalLimits(). See doo.environment.

Rate limits

Independently of the daily limits, there is a limit on how many requests you may send per minute and per hour. It applies to the Tabidoo application, the public API, and MCP tools.

You meet it in two stages:

Before the limit, responses are deliberately delayed by up to two seconds. If Tabidoo suddenly feels slow while an integration is running, this is usually why.
Past the limit, requests are rejected with HTTP 429 (Too Many Requests). Data usage counts them under Rejected requests (429).

If you see 429, wait at least a minute before you try again. Then add pauses between calls, or use bulk operations instead of one request per record.

What happens when you reach a limit

Most limits give you room above the limit: you first get a warning and can keep working, and only further above the limit is the operation stopped. Some limits stop the operation right at the limit.

Limit	Above the limit	Stopped at
Applications, tables, records per application, fields per table	Warning e-mail, you can keep working	150 % of the limit
Storage for attachments	–	120 % of the limit
Workflow runs per day	Warning e-mail, runs continue	5× the limit
Workflow time per day	Warning e-mail, runs continue	3× the limit
Long-running workflow time per day	Runs continue	3× the limit
Loaded data per day	API, workflows, and MCP are stopped at the limit; the Tabidoo application in your browser can load up to 5× the limit	at the limit / 5× in the application
Loaded attachments per day	–	at the limit
Free AI credits per month	AI continues only if you have purchased credits	at the limit
Size of a single file (50 MB)	–	at the limit
Application over its record or table limit	Warning in the application from the first day	saving data stops after 35 days

Good to know:

Reading is what usually gets blocked, not saving. The daily volume limits stop you from loading data; your existing data stays editable. The exception is the 35-day rule.
The 35-day rule is the serious one. If an application stays over its record or table limit for more than 35 days, saving data in it stops working completely.
Warning e-mails are sent at most once a day for plan limits and at most once an hour for daily limits. You can also set your own alerts in Data usage → Notifications, for example at 80 % of your daily workflow runs.
Upgrading your plan takes effect immediately and lifts the block. If you need to raise only one limit, contact us at support@tabidoo.cloud.

Technical limits

These limits are the same for every plan. They protect the platform and may change over time.

What	Limit
Size of one file	50 MB
Attachments per record	1,000
One run of a server workflow	90 seconds; on the Pro plan and higher, a long-running workflow can run as long as you set, within its daily limit – see JavaScript was terminated after 90 sec. timeout
Workflows started by other workflows	5 for one record, 50 in one chain
Workflow run log	the last 20,000 characters
Text field / Long text field	10,000 / 15,000 characters
Fields per table	1,000 `[TO CONFIRM: plan limit for fields per table]`
Options in one dropdown or checklist	1,000
Excel import	100 MB file, 10,000 columns, 400,000 rows per sheet
Records in one read request	Depends on your plan – the error message tells you the maximum. In scripts, `doo.table.getData` returns 25 records unless you set `limit` .
E-mails sent by one application	100 per minute, 1,000 per hour; at most 50 recipients in one message (longer lists are split automatically)

Which limit am I hitting?

What you see	Most likely limit	What to do
HTTP 429 / "Too many requests"	Rate limit	Wait a minute, add pauses, use bulk operations
Tabidoo or an integration is slow, no error	Rate limit approaching	Send fewer requests per minute
An integration cannot read data, saving still works	Loaded data	See Data Transfer Limit `[TO DO: link]`
Attachments will not download	Loaded attachments	Wait for the next day, download fewer files
"Javascript was terminated after 90 sec. timeout"	One workflow run took over 90 seconds	See the article
Workflows stopped running during the day	Workflow runs, Workflow time, or Long-running workflow time	Data usage → click the limit → see the top consumers
"Circular workflow call detected"	Workflows starting each other	See Behavior of Workflow
The AI does not answer	Free AI credits for the month	Buy credits or upgrade
A file will not upload	50 MB per file, 1,000 files per record, or storage for attachments	Split or compress the file, clean up old attachments
You cannot save any data in an application	Application over its limit for 35+ days	Upgrade, or delete records or tables
You cannot create another application, table, or field	Plan limit at 150 %	Upgrade, or delete what you no longer need
An Excel import fails	Import limits	Split the file
A script gets only 25 records	`doo.table.getData` default	Set `limit` and page with `skip`
A warning says the record history (audit) is over its limit	Record history over 2× the record limit of the application	See Data audit limitation
Older record history is missing	Record history	See Data audit limitation

Designing an application that stays within limits

Read only what changed. Filter on the last-change date so that integrations load only records changed since their previous run.
Filter and aggregate on the server. Data you download and then throw away still counts. If you need a total or a count, ask for it instead of loading the records.
Never read a table inside a loop. Read a lookup table once per run and keep it in a variable.
Use bulk operations. One bulk request instead of one request per record saves rate limits, time, and workflow time.
Add conditions to workflow triggers, so workflows do not run on changes they ignore anyway.
Set an alert in Data usage → Notifications before you scale up an integration – not after it breaks.