Platform Limits

Constraints that apply across the UnqorkAI platform, including file uploads, API requests, submission data, email, Build Agent, and session behavior.

Submission Data

The most common question Creators have about the submissions API is how many submissions they can read or write in a single request.

Submission Size

Each submission is stored as a single document in the database. The maximum size of a single submission document is 16 MB, a hard limit set by the database engine. This includes all field values, metadata, and any Base64-encoded file data stored in the submission.

Submissions approaching this limit might indicate that large file data should be stored externally using cloud storage instead of embedded in the submission. See the File component and File Storage component for guidance.

Submissions per Request

The 50-submission limit applies to both the default and the maximum for submission endpoints. A single request cannot exceed 50 submissions regardless of query parameters. To retrieve more than 50 submissions, paginate using the limit and offset parameters.

Pagination

Submission endpoints support limit and offset query parameters for paginating through large result sets.

Example: To retrieve records 51–100, set limit=50&offset=50.

The response includes a x-total-count header with the total number of matching records. Use this value to calculate how many requests are needed to retrieve all results.

Unqork also supports HTTP range headers as an alternative pagination method. See the API Reference for details.

Other API Endpoints

Limits vary by endpoint type. The following are common endpoints Creators access through the Plug-In component.

Data Models and Query Builder

Data Model Records

Query Builder Pipeline

Query Builder pipelines are evaluated server-side. The following limits apply per pipeline.

Smart Queries

Smart Query read operations enforce a hard cap of 10,000 records. The cap is applied at two points. At structural validation, a limit stage is automatically injected if the query specifies none. At execution, any limit value above 10,000 is rejected. Parameter values passed to Smart Queries must be primitives or arrays of primitives. Object values are not supported.

File Uploads

End-users submit files through modules. The limits that apply depend on the storage used.

Any file-related or API request lasting longer than five minutes will fail.

Upload Size Limits

Administrators configure the maximum file size for end-user uploads in Environment Administration.

File Component Storage Paths

The File component stores uploaded files through one of two paths, determined by the Parse Files on Upload setting.

Cloud storage (Parse Files on Upload = OFF): Files are stored in the environment's cloud storage provider. The Unqork server enforces a 100 MB per-file limit server-side, regardless of the Max File Size setting on the component.

Base64 in submission (Parse Files on Upload = ON): Files are Base64-encoded and embedded directly in the submission document. Base64 encoding inflates binary file size by approximately 33%, and the encoded data counts against the 16 MB BSON submission document limit. The maximum file size depends on how much other data the submission contains. A submission with minimal other field data can accommodate a file of approximately 12 MB binary; submissions with more field data have less headroom.

Execution Channel Upload Limits

Administrators configure upload limits for Service Execute and Execute via API channels in Environment Administration.

Upload Errors

If an uploaded file or request payload exceeds the enforced limit, the server returns a PayloadTooLargeError: request entity too large error. The upload is rejected before processing; the file itself is not stored. To resolve the error, reduce the file size or check the Max File Size setting in Environment Administration. For Base64 submissions, consider switching to cloud storage (Parse Files on Upload = OFF). Switching to cloud storage lifts the effective limit from the BSON submission cap to the 100 MB per-file server limit.

File Downloads

End-users download files from cloud storage through the Unqork server, which proxies the stream directly from the storage provider to the browser. Unqork does not enforce a file size cap on downloads. Download availability and throughput are governed by the cloud storage provider and network conditions.

File Imports

Data Collections

Creators import CSV files into Data Collections through the UnqorkAI platform.

Module and Application Blueprints

Application definitions are imported as JSON through the Unqork API. The import endpoint accepts JSON request bodies up to 100 MB by default. This limit is configurable per environment using the UNQORK_SERVER_MERGE_ENDPOINTS_JSON_PARSER_LIMIT environment variable.

File Processing

The Unqork server supports server-side file operations through the /fileUtils API, including creating ZIP archives, extracting ZIP files, and converting between JSON and CSV. The following limits apply per request.

External Service File Calls

When Creators call external services through the Plug-In component, separate limits apply to the outgoing request and the incoming response.

Outgoing requests: Unqork does not impose a limit on the payload sent to an external service. The external service's own limits apply.

Incoming responses: Unqork limits the response it accepts back from external services based on the Expect Binary Response setting.

Request Payload Limits

These limits apply to all API requests sent to the Unqork server, regardless of which component or service initiates the call.

Style Assets

Administrators upload style assets through the Style Editor, including images, fonts, and CSS files. The following limits apply.

Accepted File Types

By default, Unqork accepts the following file types for end-user uploads. Administrators can configure a different set of allowed extensions per file manager in Environment Administration.

To restrict accepted file types on a specific File component, use the File Pattern setting (for example, .pdf,.png).

Security Processing

All uploaded files go through the following checks before being stored:

• Antivirus scan: Files are scanned for malware and rejected if infected.
• MIME type validation: Files are rejected if their MIME type does not match their extension.
• Magic byte check: The file's binary signature is verified against its declared type.
• SVG sanitization: SVG files are sanitized to remove embedded JavaScript before storage.
• HTML sanitization: HTML files are filtered to remove XSS content before storage.

Email

Email workflow steps route through AWS SES. The following limits apply per message.

Build Agent

The following limits apply to Build Agent interactions in the UnqorkAI platform.

Chat Input and Output

File Attachments

Creators can attach files to Build Agent messages. The total size of all attachments per Task cannot exceed 10 MB. Additional per-type limits apply.

Session and Authentication

Session Timeout

Both timeout values are configurable per environment in Environment Administration.

Account Lockout

Both values are configurable per environment in Environment Administration.

Passwords

Password length requirements are configurable per environment in Environment Administration.

Rate Limiting

Rate limits are configured per environment by an administrator and vary by customer.

Administrators can view and update this setting in Environment Administration. Applications hitting rate limits should contact their environment administrator to review the current configuration.

Browser Storage Component

The Browser Storage component stores data in the browser's localStorage. Storage limits are enforced by the browser, not by Unqork.

Keep data stored in the Browser Storage component small. Avoid storing large arrays or deeply nested objects.

Platform Updates

When the Unqork platform undergoes an infrastructure update, long-running processes have a 5-minute graceful shutdown window to complete. The window applies to both scheduled platform releases and unscheduled infrastructure changes.

The following process types are subject to this window:

• Server-side execution (SSE) modules
• Automated Workflows
• Timers (scheduled and repeating timers configured in the Timer component)

Processes that do not complete in 5 minutes are interrupted when the update takes effect. Creators and end-users cannot extend the window or terminate in-flight processes manually.

To reduce the impact of interruptions:

• Avoid scheduling time-sensitive automated workflows or timers during known platform maintenance windows.
• Build retry logic into workflows that call external services, so they can recover if an in-flight request is cut short.
• After a platform update, check downstream systems for any processes that did not complete and rerun them as needed.