Connector limits

Check time and size limits for working through the Connector. Unless stated otherwise, these values apply to Free and Max.

On this page

These time limits apply when connecting

ItemValue
Complete Connector sign-in, from starting in the application to returning from TEISENDA10 minutes, in the browser where it started
Decision on the consent page10 minutes from displaying the page, one decision per display
A connection's Spacesat least one Space or the option for future Spaces

How long the application's authentication lasts

ItemValue
Application authenticationone hour; the application can then renew it
Authentication renewalpossible until 60 days after the last renewal; each renewal can be used once and is replaced by a new one when used
Period without use after which the card marks a connection as unused60 days; see Authentication and unused connections

How quickly changes in TEISENDA take effect

ItemValue
Changes in TEISENDA: a connection's Spaces, ending a connection, locking a SpaceThe Connector notices them within up to one minute. The app applies them immediately to every tool call.
Changed tool catalogue or instructionsThe Connector notices them within up to one minute.

These limits apply to each call

ItemValue
Tool call durationtwo minutes
Request size sent to the Connector8 MB
Requests per second10 per IP address. From Claude and ChatGPT networks, TEISENDA instead counts 10 per authentication and 50 per address for unauthenticated requests. TEISENDA allows brief bursts above these limits and rejects sustained excess.
Calls without valid authentication from one IP address30 in 10 minutes; the address is then blocked for one hour. Claude and ChatGPT networks are exempt.

These limits apply to files and uploads

Exceeding a limit may produce the general missing or invalid argument message. The troubleshooting guide explains causes and solutions.

ItemValue
Files per call to hosting_put_files200 files and 3 MB. More files trigger the message about the argument files; more data triggers That's too much for one call. Split the files across several calls.
Paths per call to hosting_delete_files200. More trigger the message about the argument paths.
Files per response from hosting_list_files100; the response gives next_offset to continue
File that hosting_read_file can readup to 200 KB; a larger file triggers The file is too large to read here. Each call returns at most 40,000 characters, and the response gives next_offset to continue.
File pathsrelative, with forward slashes; at most 240 characters, 12 levels and 100 characters per name. No names starting with a dot except .well-known in the root folder.
Drafts per projectat most one; the app interface writes to the same draft
Upload address from hosting_create_uploadValid once and for 15 minutes; the result gives the time under expires_at. The archive can be up to 200 MB, must be zip, tar or tar.gz and is sent to the address by HTTP PUT.

Check hosting limits too

File and version sizes, retained versions and custom domains also have technical hosting limits. Plan limits can be lower.

These limits apply to names, domains and redirects

ItemValue
Project name1 to 80 characters, no control characters
Custom domain hostnameat most 253 characters, no IP address, without https:// or a path; not in the zones teisenda.com, teisendapages.com or teisendahosting.com
Redirects per project200 rules. A source can have up to 500 characters, a destination up to 1,000, and the allowed statuses are 301, 302, 307 and 308. Exceeding any of these limits triggers The list was not saved: TEISENDA reports a source or destination that is too long as invalid without mentioning the length.
Paths that cannot be a redirect source/.teisenda and everything below it, /.well-known/acme-challenge and everything below it. These also trigger The list was not saved:

Tools also respect plan limits

The values are listed under Hosting limits. Free allows a total of 3 publications per Space; uploading and republishing an earlier version do not count. A Space is a shared workspace in the app.

Warning

A newly completed version can permanently displace the oldest versions. The published version and backups are protected.

When publications are used up, writing and uploading new files are blocked. Previously published versions can still be republished.

What happens to a version that is too large?

A version that is too large after extraction, has too many files or does not fit in storage is discarded when completed. Older versions remain. max_bytes in the upload address result gives the allowed archive size. The plan limit troubleshooting guide explains the messages.

When does TEISENDA send an email about low storage or project capacity?

Usage increases through tools can trigger the same email notices as changes in the app. See Usage emails for timing, recipients and repeat notices.

Do tools keep working in a paused Space?

If TEISENDA pauses a Space after a subscription ends, the hosting node serves none of its websites. Tools work as in any other Space; the Connector does not treat a paused Space as locked.

  • Free plan limits apply, including publications from the previous plan. If they are used up, TEISENDA rejects hosting_put_files, hosting_create_upload and hosting_deploy for a ready version.
  • No result says that the Space is paused and visitors see an error page. The field offline refers to the individual project's switch and remains false.
  • hosting_create_upload does not receive an address in a paused Space and responds with The project is offline.
  • Deleting projects and removing domains remain possible. Switching to Free and subscribing again happen in the app; no tool does this. See Hosting limits.

Set backups in the app

A backup is retained when new versions are added. Set or remove its backup status in the app's version menu; the Connector has no tool for this.

Warning

Deleting the whole project also deletes its backups.

The Connector and app log usage

The Connector and app keep several usage logs. See Connector and app logs for their contents and confirmed retention periods.

Next steps