FSM Recurrence Deletion and Retirement Behavior
Deleting occurrences in Field Service Management (FSM) has different consequences from hiding recurrence controls or pausing processing. For recurrence concepts and constraints, see FSM Case and Task Recurrence.
Deleting a non-primary occurrence using normal NetSuite deletion records its index as deleted. FSM uses that information to avoid recreating the occurrence during later series maintenance.
If the primary is deleted, FSM uses the next remaining occurrence to continue the series. If no later occurrence remains, the recurrence definition is marked for deletion.
Delete Future Instances ends the series before a selected later occurrence's start date and requests background deletion. On the primary, it uses the definition's start date and also marks the definition for deletion. For occurrences that follow the series pattern, the action includes the selected occurrence and those after it. An individually rescheduled occurrence can have a different date from its position in the pattern. The action redirects the user to NetSuite Home with background work still outstanding.
Removing occurrences, including removal caused by shortening a series, does not use the same Not Started restriction as field and date propagation. Started or completed work is not protected by that propagation rule. Normal record-deletion restrictions still apply. For example, FSM's case-deletion guard blocks removal when a child task in its checked snapshot has started or contains time or consumables. A deletion failure can leave partial changes. A request to delete a series therefore does not establish that all its records have been removed.
Normal FSM case deletion queues removal of the linked child tasks returned by its lookup through separate Work Order processing. It marks those children for destruction and clears their case links before the native case deletion finishes. Parent and child removal is not atomic. A later failure can leave detached or queued children. This includes manual tasks as well as those created by Program. The standard lookup is limited to the first 1,000 results, so large child sets require a completeness check. Verify the original case and task IDs to establish the actual result.
End Type: None means that generation remains open-ended. It is not a cancellation option. Completing or closing an occurrence also does not end the recurrence definition.
Administration and Retirement
There is no standard recurrence-definition list or customer-facing series management page for reviewing all patterns, their saved values, and errors together. Case and task recurrence controls expose part of the definition. Investigation can require checking occurrence fields and linked errors. Privileged technical access does not make the hidden definition an ordinary editable customer record.
The feature does not provide a supported bulk pause or retirement action for all definitions. The per-series Delete Future Instances action removes service records. It is not a preservation-based pause. Deleting only the primary normally promotes another occurrence and can leave the series running.
Hiding the controls, marking a supporting definition inactive, clearing Create/Update Instances, or completing individual work is not a reliable account-wide stop. Existing unfinished definitions can qualify for maintenance again. A deployment-level interruption leaves the recurrence data in place and must not be treated as permanent retirement.
Where a script deployment is disabled as an administrative intervention, upgrade behavior depends on the deployment settings applied by the bundle update. NetSuite supports both overwriting and preserving existing deployments. See Bundle Object Preferences. A saved local deployment setting alone does not establish a durable product-level off switch. Shared deployment controls and update consequences belong in FSM Script Reference.