Script Limits
Because cortex scripts execute within a multi-tenant environment, there are limits in place to ensure that runaway scripts do not monopolize shared resources.
Below are the default limits enforced per Cortex script execution
Description | Default Limit |
Job timeout (maximum execution time for a Cortex Job) | 10,000 milliseconds |
Route timeout (maximum execution time for a Cortex Route) | 5,000 milliseconds |
Trigger timeout (maximum execution time for a Cortex Trigger) | 5,000 milliseconds |
Notifications (maximum number of email, push, and/or sms notifications) | 100 |
Callouts (maximum number of http module requests per script execution) | 5 |
Callout timeout (maximum time for an http module request) | 30,000 milliseconds |
Callout request size (maximum size for an http module request) | 524.288 Kilobytes |
Callout response size (maximum size for an http module request response) | 524.288 Kilobytes |
Execution depth (maximum levels of nested cortex script executions) | 4 |
Max operations (Jobs, Triggers, and Routes) | 1,000,000 |
Description | Default Limit |
Job runs (maximum number of job runs per day) | 24 |
Description | Default Limit |
Cortex script size (maximum character limit of a cortex script) | 50,000 characters |
In addition to the above limits, the following limitations are enforced within Cortex scripts.
- Callouts to Cortex API endpoints are not allowed within a Cortex script. Use the CortexObject class and its methods for interacting with Cortex Objects in scripts, instead.
- Callouts are not allowed in in-line triggers
- Triggers are not allowed on the Views, Scripts, Org and Objects objects
Last modified 1yr ago