Operations
- The default operation timeout is typically 40 seconds.
Files
- Fusion’s total processing capacity for files is 1 GB. The limit is based on a total memory cost. Every operation contributes to that cost. If a single file of 400 MB is downloaded and uploaded then the total cost to the file capacity would be 800 MB.
- Organizations on the Workfront Ultimate plan have access to increased file processing beyond 1 GB. The Fusion platform can support individual files up to 15GB for a single action (e.g. upload file), but there are other factors that affect data transfer. The file size limit of single action depends on the web service Fusion connects to. Data transfer is the total processing for a single execution. This means multiple actions in a single execution contribute to the total data transfer. Fusion will process files until the execution limit of 40 minutes is reached.
For more information, see Working with large files.
Server Memory Usage
-
Server memory usage for a single execution is limited to 1 GB.
Many factors, such as large files or complex modules, can affect server memory usage in ways that are difficult to predict or control. Because of this, your scenario execution may exceed the 1 GB memory limit, even if the scenario follows all other performance guardrails. Exceeding the memory limit causes the execution to fail.
Webhooks
-
The default maximum size of a payload is 5 MB.
-
Webhooks are limited to 100 requests per second. When this limit is reached, Workfront Fusion sends a 429 (Too Many Requests) status.
-
Workfront Fusion stores webhook payloads for 30 days. Accessing a webhook payload more than 30 days after it was received results in the error “Failed to read file from storage.”
-
Webhooks are deactivated automatically if either of the following applies:
- The webhook has not been connected to any scenario for more than 5 days
- The webhook is used only in inactive scenarios, which have been inactive for more than 30 days.
-
Deactivated webhooks are deleted and unregistered automatically if they are not connected to any scenarios and have been in deactivated status for over 30 days.
Execution history
- Execution history logs are limited to a size of 100 MB. If the execution history exceeds this size, only the first 100 MB will be shown.
- If a scenario has multiple concurrent executions. only 5 executions display in the Executions area of the scenario details page. This is true even when more than 5 executions are running.
Incomplete executions
- Incomplete executions are limited to a total size of 500 MB. If the 500 MB limit is reached, no more incomplete executions will be stored.