Limits & quotas

Limits & quotas

Every cap, quota, and rate limit the Telenow App Platform enforces — with the exact number, the HTTP status you get at the cap, and whether the value is rejected (the request fails), clamped (silently pulled into range), or truncated (the extra data is dropped but the request succeeds).

These guardrails exist so one app's runaway loop can't starve other tenants. They are generous for legitimate apps. Caps are per (org, app) unless noted — your app sees its own counts in one org, isolated from every other install.

A note on "soft" caps: some counts (the row cap, the proxy/circuit-breaker state, the Data-API rate buckets) are process-local and cached, so on a multi-node cluster the effective limit may overshoot slightly before it settles. They stop abuse; they are not billing.

Data store & reads

The row count is soft and process-local, cached with a 60-second TTL. A cluster may overshoot the cap slightly, and freed rows (deletes) free up capacity within about one minute as the cache refreshes.

The cap covers every writer, not just the REST API: dashboard-bridge creates, agent object.create tools, inbound webhooks, workflow create-object steps, event-rule upserts, and public-link form submissions. That last one is the one to think about when you issue a form link to someone outside the org — it is the only write into your store an unauthenticated caller can reach, so the row cap is what bounds a link that gets shared further than you intended. Prefer single-use links, and keep expiries short. (On builds before mid-2026 the form path skipped the cap entirely.)

POST /api/app-data/patient
Authorization: Bearer <app key>

HTTP/1.1 413 Payload Too Large
{ "success": false, "error": "app data store is full (max 100000 records per app)" }

Blobs / files

A put over any of these is rejected. The byte cap and the file-count cap are both enforced — a flood of tiny files is blocked by the 10,000-file cap even though it fits under 1 GB.

Data API rate limit

The programmatic app-key Data API (/api/app-data/...) is rate-limited with a token bucket, per (org, app):

The in-dashboard data proxy (member-authed — a human is signed in) is not subject to this limit. Only the programmatic app-key Data API is rate-limited here.

GET /api/app-data/patient
Authorization: Bearer <app key>

HTTP/1.1 429 Too Many Requests
{ "success": false, "error": "Data API rate limit reached — slow down", "retry_after_secs": 1 }

Tools

Note: timeoutSecs clamps to 1–30 seconds (not 1–10). A 15-second default applies when you omit it.

Sandbox runtime (js / sandbox handlers)

The hardened code runtime applies its own hard limits, independent of timeoutSecs:

Automation

Manifest caps (validated at upload — rejected otherwise)

every is a simple <positive int><unit> duration — unit in {m | min, h | hr, d | day}. No seconds, no weeks, no cron. Any multiple is allowed (e.g. 90m, 6h, 2d), but anything under 5 minutes is rejected at validate.

"schedules": [
  { "key": "nightly", "every": "24h", "handler": { "kind": "rule", "object": "...", "key": "...", "map": {} } }
]
// "every": "2m"  → rejected (under the 5-minute floor)

Inbound hooks

Workflow runtime

Step outcomes: a 5xx response or a transport error retries (backoff absorbs transient failures); a 4xx response and an update-object with no matching row are non-fatal (the step is Done).

Agents / knowledge bases / eval

Manifest caps (reject the upload otherwise)

Runtime cap

This runtime cap is enforced across every create path — dashboard create, the app-key POST /api/app-agents, and whole-team create. It is distinct from the 50 manifest-template cap (agents[]): the 50 caps how many templates a manifest may ship; the 100 caps how many real agents you may provision.

Eval

Campaigns

HTTP proxy (telenow.http / bridge)

The server-side proxy your dashboard UI calls through (telenow.http(...)). State is process-local (single node).

A 4xx response counts as "up" — it does not trip the breaker.

Package / upload

All of these are rejections, not truncations — the whole package upload fails if any is exceeded.

Session token & stream tickets

Next

• Data & objects
• Agent tools
• Events, webhooks & workflows
• External backends & the app-key REST API
• Packaging & distribution