Monitoring and Interpretation
Use script records, execution statuses, logs, and record-page banners to monitor processing and interpret the results.
Script and Deployment Records
To identify scripts, go to Customization > Scripting > Scripts with the appropriate administrator permissions. The script record lists its deployments. Use the IDs in Supplied Scripts and the deployment tables to distinguish similarly named entries. Execution Log entries contain messages written by the relevant script. The deployment's Log Level controls which levels are retained. See SuiteScript Monitoring, Auditing, and Logging.
Go to Customization > Scripting > Scripted Records to identify User Event and record-level Client associations. This page does not list every background job that can change a record. See SuiteScript FAQ.
Scheduled Execution Status
Go to Customization > Scripting > Scheduled Script Status. Filter by script, deployment, and time to identify the submitted execution. Pending means submitted and waiting. Processing means executing. Complete means the execution finished normally. The Not Scheduled deployment setting describes on-demand submission and is separate from these execution states. See Scheduled Script Status Page.
The following table explains log outcomes written by the dedicated FSM runner.
|
Log Outcome |
Meaning |
|---|---|
|
Ready |
The dedicated processing loop started. The log shows its time budget. |
|
Assess |
The assessor returned a count of actions. This count can differ from the number of distinct records. |
|
Dispatch |
An action was selected to run. This entry precedes its result. |
|
Skip |
An unrecovered matching error prevented the action from being attempted in this pass. |
|
Defer |
An ignorable error or record collision occurred. The runner does not report another error record in this branch. |
|
Reschedule |
The runner requested continuation after reaching its time or usage budget. |
|
Blocked |
Every action in the fully examined batch was skipped because of unrecovered errors. |
|
Complete |
No actions remained in the latest assessment. This does not rule out records excluded earlier by an error filter. |
These log outcomes are separate from NetSuite execution statuses. The dedicated runner's percentage reflects elapsed processing time against its budget. It does not reliably indicate the percentage of business records successfully processed.
Record Page Banners
When the relevant schedule view is active, saved case, CRM task, and asset forms can display pending-work information. Some messages are calculated from whether work remains eligible. Other messages use scheduled-instance status for generated callbacks. A pending banner can therefore appear without establishing that an execution is running.
The supplied task banner checks Notification, Time Zone, and Recurrence work. It does not provide a comprehensive status display for every script that can affect a task. Case and asset banners also cover selected operations. Banner absence does not establish that every related process finished.
For execution failure details, combine the relevant log and instance context with the Field Service Error record, if one was captured. The associated feature topic explains the failure's effect on the business outcome.