orchestrator
2024.10
true
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Increasing the Size Limit of Package Files
- Setting up Encryption Key Per Tenant
- GZIP Compression
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Increasing the Size Limit of Package Files
Orchestrator User Guide
Last updated Dec 4, 2024
Increasing the Size Limit of Package Files
Regardless of the storage you use to keep your packages (activities, automations, and libraries), the maximum file size per upload is 28.6MB - a limitation given by IIS.
In some cases, when trying to upload packages larger than the default size, a 404 error can be thrown. In other cases, the Robot can crash.
This page shows you how to customize this size, according to the type of storage you are using for your artifacts.
If you want to be able to upload files larger than 28.6MB, perform the steps below:
- Stop your Orchestrator Instance from IIS.
- Navigate to the config file and open it using an editor such as Notepad++.
- Add the
<requestLimits maxAllowedContentLength="<valueInBytes>"/>
key, using a custom value, such as314572800
(300MB). - Save the file and start the site again. You can now upload files with a maximum size of 300MB.