IFTTT Filter logic and trigger-to-action latency

Conditional Execution Overhead

IFTTT Applets for Pro and Pro+ tiers utilize Filter code to implement JavaScript-based logic. This allows for the evaluation of trigger ingredients to determine whether a specific action should be dispatched or suppressed.

Because Filter code is executed on IFTTT servers after a trigger is received but before the action is triggered, there is a potential for processing overhead. While polling-based triggers have inherent latency, it is unclear how the complexity of the JavaScript logic within a Filter affects the final dispatch time of the action.

Does the execution of complex Filter logic introduce measurable latency between the trigger event and the action dispatch? Are there documented execution timeouts or performance limits for JavaScript within the Filter feature?