Usage Limits

The below tables in this article indicates the various usage limits of the Axway AMPLIFY platform and to which environments they apply.

Flows

Limit Name Limit Description Scope
Flow max request size 8 MB

The maximum size of the input request to the flow trigger. This limit is for each flow execution.

If the limit is exceeded, the flow execution will result in a 429 HTTP error code.

Request
Flow max step execution value log size 2 MB

After each flow step is executed, the resulting value of the step execution is logged and available to view via the flow execution audit trail. For connector requests or similar steps, this value will include a request/response payload, header information, and so forth.

If the limit is exceeded, the flow will still complete execution successfully, but the step execution value will not be available in the execution audit log.

Flow step

File Streaming

Limit Name Limit Description Scope
Streaming API Response Payload Size (File Download/File Upload) 6 GB

This limit applies to streaming APIs, for example, GET /files/{id}, GET /bulk/{jobId}/{objectName} and others. This limit is for the maximum download size of a file from any such APIs.

If a file greater than 6GB is attempted to be downloaded via such an API, then the request will fail with a 429 HTTP error code.

Response/Request
File upload/download API timeout 3,600 seconds

This limit is the amount of time after which a file upload or download API will timeout. For example, if a large file is being uploaded and the internet connection used between the client and Axway AMPLIFY is prolonged, the client will need to have the file uploaded within the specified limit.

If this limit is exceeded, the upload or download request will fail with a 429 HTTP error code.

Request

Events

Limit Name Limit Description Scope
Event ingest payload size 8 MB

The Axway AMPLIFY platform provides the functionality for connector instances to serve as proxies for events received or polled from the service provider's API endpoint. These events, once received by Axway AMPLIFY, are temporarily persisted for further processing and dispatch to the owner of the connector instance. This limit imposes the maximum payload size of each event received by Axway AMPLIFY on behalf of our customer.

If this limit is exceeded, the event payload will not be temporarily persisted for processing or dispatch.

Request

API Requests/Responses

Limit Name Limit Description Scope
API Request/Response Payload Size (non-file upload) 8 MB This limit will be applied for the request to and response from all non-streaming APIs, platform as well as connectors. An example of a platform API is "GET /formulas/{id}," and one for a connector API is "POST /hubs/crm/accounts."

If this limit is exceeded for the request or response payload, the API will result in a 429 HTTP error code.
Request and Response
Javascript Execution Time 30 sec This limit is for the execution completion time for a Javascript execution request. There are currently three ways to make such a request, via a pre-hook or post-hook for a connector or connector resource, via Javascript configured for a connector (mapping) mapping and via a script step in the v1 flow execution engine.

If this limit is exceeded, wrapping requests (connector API, mapping, or flow script step) will result in a 500 HTTP error code.
Request

Related Links