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
Job timeout (maximum execution time for a Cortex Job)
Route timeout (maximum execution time for a Cortex Route)
Trigger timeout (maximum execution time for a Cortex Trigger)
Notifications (maximum number of email, push, and/or sms notifications)
Callouts (maximum number of http module requests per script execution)
Callout timeout (maximum time for an http module request)
Callout request size (maximum size for an http module request)
Callout response size (maximum size for an http module request response)
Execution depth (maximum levels of nested cortex script executions)
Max operations (Jobs, Triggers, and Routes)
Job runs (maximum number of job runs per day)
Cortex script size (maximum character limit of a cortex script)
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