Limits

The limits the system applies to run time, rows, request rates, bulk runs, JS actions, views and configuration.

3 min read

The limits below protect the connected databases and keep the tool responsive. Some values can be set per action; the others are system-wide.

Running actions

Limit	Value	Where to change it
Maximum run time (timeout)	30 seconds by default; settable from 0.1 to 300 seconds	Timeout (seconds), in the action’s General card
Maximum rows returned	10,000 by default; settable from 1 to 1,000,000	Max rows, in the action’s General card
Size of returned data	10 MB per run	System-wide
Run rate	60 runs per minute per user per action by default	Deployment-wide setting

When a result is cut at the maximum row count, the run page shows “Showing only the first N rows — narrow the filters to see everything”. The filter box in the result table only filters the rows that were loaded.
When the rate limit is exceeded, the interface shows “Too many requests. Try again shortly.”
The result table switches to virtual scrolling at 500 rows or more, so large tables still scroll smoothly.
Read-only actions run inside a read-only transaction: the database itself rejects any write.
On PostgreSQL, a statement that waits more than 3 seconds for a lock is cancelled, and a transaction left idle for more than 10 seconds is closed. This prevents the tool from stalling applications that share the database. MySQL also uses a 3-second lock wait timeout.

Limit	Value
Parameter sets in one bulk run	Up to 10,000
Job list refresh	Every 2 seconds while jobs are running
Schedule expression	Five-field cron (minute hour day month weekday), in UTC

Schedules do not catch up on missed runs. If the system pauses for a while, a schedule runs once when it resumes.
Add to the queue and Bulk run are only available for SQL actions in Writes data mode; read-only actions and JS actions run directly.
Background runs only keep the row count and errors, not the returned data.

Limit	Value
Calls to other actions in one run	50
Nesting depth (JS action calling a JS action)	3 levels
Run time	30 seconds
Memory	128 MB

JS actions run in a sandbox with no network access. JS actions cannot be queued or scheduled yet. See JS actions.

Limit	Value
Rows passed to a transformer	Up to 50,000
Bundle size of a view at publish	1 MB
Action calls from one screen	20 calls per 10 seconds

Limit	Value
Cache for tables, columns and the relationship diagram	5 minutes
Tables drawn at once in the relationship diagram	60; if there are more, select a table as the center
Expansion depth around the center table	3 steps
PEM certificate file size	200 KB
HTTP data source timeout	15 seconds by default, up to 120 seconds
Allowed hosts of an HTTP data source	Up to 50

Limit	Value
Password length	At least 12 characters
Wrong current password when changing password	5 times in 15 minutes, followed by a waiting period