How Timeouts Work

This article explains how timeouts are handled in a logic and in libraries which call each other:

  • The executed element timeout is always honored.

  • Library elements timeouts are ignored. What matters is the time the logic element is executed, including library calls.

  • Elements timeouts are always capped by the maximum timeout configured at the cluster level.

    • This setting defaults to 900s (15 min).

    • It can be increased by Pricefx Support via the setting formulaEngine.script.maxTimeoutInSec.

  • Special cases:

    • Since 10.0: PA Data Loads, PA Distributed Calculation, DMModel Calculations and Model Calculations completely ignore the timeouts in their logics but not in their libraries.

    • Since 10.2: PA Data Loads, PA Distributed Calculation, DMModel Calculations and Model Calculations completely ignore the timeouts in their logics and in the libraries they use.

    • Before 10.2: Elements timeout is set when the logic is pushed/saved to the partition. So if you increase the maximum timeout in your cluster, you need to resave your logic.

    • If an element just calls a library and the library has a higher timeout than the element, then the library element timeout is honored.

Found an issue in documentation? Write to us.