Skip to main content

XProtect Smart Client

[en] Issue: Actions in the script stop running halfway through

Senest opdateret: Anslået læsetid: 1 min.
Version2026 R2
SprogDansk
[en] Cause

[en] To protect application stability, each execution of a script body or event trigger is subject to runtime guardrails:

  • [en] Maximum 100,000 statements per run.

  • [en] Maximum run time of 30 seconds per run.

  • [en] Maximum 30-second pause for Thread.Sleep().

  • [en] Maximum 60 executions per minute for an event trigger.

[en] If a script exceeds any of these thresholds, the engine stops that specific run immediately to prevent the client from freezing or looping indefinitely.

[en] Solution
  • [en] Ensure that loops have concrete exit boundaries and do not exceed the statement limit.

  • [en] Avoid scripts that trigger infinite loops (for example, an event trigger that reloads configuration, which subsequently triggers the same event trigger).

  • [en] Check the Script in use section on the Smart Client scripts settings tab. If the script was stopped by limits, the Status field reports how many statements ran before the script stopped (for example, “Stopped after 100000 statements in 1200 ms.”).