Manage SuiteScript 2.x governance units to prevent script termination in scheduled and map/reduce scripts

In-depth guide

Steps

1. Call runtime.getCurrentScript().getRemainingUsage() at checkpoints in your script to monitor remaining units before expensive operations
2. For scheduled scripts, implement a rescue pattern: when remaining units fall below a safe threshold, save state to a custom record or script parameter and re-schedule the script to continue from that checkpoint
3. For map/reduce scripts, take advantage of built-in yielding — the platform automatically handles checkpointing between map, shuffle, reduce, and summarize stages, each with its own governance reset
4. Identify high-cost API calls (e.g. record.load, search.run) by checking the governance cost table in NetSuite documentation; batch or replace expensive calls where possible
5. Use search.runPaged() instead of search.run().each() for large searches to avoid exhausting governance on a single search traversal