Maximum execution time I’ve been trying to correct...

I’ll trace where the script can run past Google Apps Script’s execution limit, fix the actual long-running path rather than just changing a timeout value, then give you a downloadable updated script.

I found the script already has “soft deadline” guards, so the problem isn’t a missing timeout setting. One path can still keep expensive work alive after the safe budget is nearly gone, and I’m checking the fetch/retry flow for the same issue before patching it.

The failure path is clearer now: the late “research sidecar” can start near the end of AutoFill and then run an uncapped full-history filter, bypassing the script’s own soft deadline. I’m fixing that plus the network-start guards and the custom-function preview budget so one slow source can’t push the whole execution over the platform limit.

The patched build now passes a full JavaScript syntax check. I’m doing one last diff/guard audit so I don’t hand you a file that merely moves the timeout somewhere else.

Fixed. The real issue was in the execution-budget wiring, not just a single timeout value: the KSR history/filter path could run without an internal wall-clock stop, and its deadline logic could extend work instead of constraining it. (TennisLocks_v1555.txt) (TennisLocks_v1555.txt) I also corrected the overly long Match Preview soft deadline and tightened the late AutoFill/KSR work. (TennisLocks_v1555.txt) (TennisLocks_v1555.txt)

The updated v1556 now caps the KSR loop, prevents new slow network calls near the execution deadline, gives AutoFill a larger safety reserve before starting the research sidecar, and uses a much shorter Match Preview budget. I also ran a full JavaScript syntax check and a deadline-guard smoke test; both passed.

Download the updated script:
TennisLocks_v1556_execution_fix.gs

TXT copy