“script stopped after 2000 ms (infinite loop?)” in Senzoukria scripting

What you see

The script console and the pipeline strip show the run as failed with “script stopped after 2000 ms (infinite loop?)”. If the sandbox never answered at all, the error is “sandbox unavailable: the {scheme} protocol served nothing within {ms} ms (app launched outside Tauri?)”.

Why it happens

Scripts run in one sandboxed worker with no network, no file access and no broker API. A run that does not answer within its budget is stopped so a broken script cannot freeze the chart. Most often the cause is a loop that never ends, or a loop over all bars nested inside another loop over all bars. The two failures are kept apart on purpose: for two and a half months, a sandbox that did not start had been read as a slow script. Starting the Python engine is timed separately and is not counted in the 2-second budget.

How to fix it

• Look for while loops whose exit condition can stay false, and for a counter that is never updated.
• Replace nested loops over all bars with a single pass that carries running values.
• Test on a shorter chart range to see whether the time grows with the number of bars.
• Use the Script assistant: it can run the script, read the real error and propose a fix.
• For the sandbox message, restart the app; it indicates the sandbox protocol did not serve anything.

What it is not

• Not a crash of the app: a broken script never kills the chart.
• Not a syntax error: those point to a line (“Failed at line {line}”).

When to contact support

Still stuck after these checks? Use Menu → Report a problem, or post on the Senzoukria Discord. Attach a minimal script that reproduces the stop and say on which chart and timeframe it runs.