Override Default Timeout for Groovy Scripts
When you use Groovy code (whether short expressions or multi-line scripts) for business logic, you have the option of overriding the default timeout configured for Groovy processing. You might want to do this if you expect your script's processing time to exceed the default Groovy timeout at runtime.
You can specify your own timeout for Groovy code that calculates a formula field's value or a field's default value. You can also change this setting in business rules when you define field-level or object-level validation rules, field or object triggers, and object functions.
The default timeout for each of these options varies and should work for most scenarios. Consider changing the default timeout only if your script's processing time will overrun the default duration and you run the risk of the connection timing out before your business logic can be executed. If you anticipate a fairly long processing time, you might also want to enable polling to prevent endpoint requests from being terminated because of (say) gateway or browser timeouts.
Business Object Functionality | Default Timeout (in seconds) | To Change the Default Timeout, See: |
---|---|---|
Calculate a field's default value when using an expression | 60 seconds | Set a Default Value for a Field |
Calculate a field's value using a formula | 5 seconds | Add a Formula to a Field |
Object and field triggers | 60 seconds | Object Triggers |
Object and field validators | 60 seconds | Object Validators for Business Objects |
Object function | 60 seconds | Object Functions for Business Objects |