Loading

Field Service: Bundle Parent Appointment Not Deleted After Members Are Unbundled When Cancellations Occur in Separate Transactions

Fecha de publicación: Oct 6, 2026
Descripción
Salesforce Field Service Appointment Bundling groups related Service Appointments under a single bundle parent (a Service Appointment with IsBundle = true). When bundle members are updated with a status that triggers unbundling (such as Canceled or Unscheduled), Field Service removes each member from the bundle and, if configured with Delete Empty Bundles enabled, deletes the bundle parent once it becomes empty.
This article applies to orgs where bundle member Service Appointments are canceled or updated through an automation or integration - for example, a dispatch system or REST API integration that cancels each appointment in a separate request - and where two or more members of the same bundle are updated through separate requests that reach Salesforce at nearly the same time.

Symptoms:
  • The bundle parent Service Appointment remains in the system after all members appear to have been removed or canceled
  • One or more members remain associated with the bundle after cancellation
  • A validation error or unexpected field-update failure is returned during the unbundling process
  • The bundle parent is not deleted even though it has no remaining members
Solución

Root Cause

Field Service evaluates bundle membership each time a member Service Appointment is updated. When members are canceled through separate requests, each runs as an independent transaction with its own commit point. If the second cancellation commits while the unbundling triggered by the first is still in progress, the two transactions overlap. The unbundling process for the first member captures a snapshot of the bundle's state - including the statuses of all remaining members - at the start of that transaction. If the second member's status changes and commits after that snapshot is taken but before the unbundling process has completed, the snapshot no longer reflects the second member's current state. Field Service then attempts to apply the configured Status on Removal from Bundle to the second member based on the outdated snapshot. If a validation rule or field restriction prevents that status update from being applied - because the member has already reached a terminal state such as Canceled - the unbundling process cannot complete, the bundle is not emptied, and the parent is not deleted.

If separate requests cannot be avoided, sequence them so that each subsequent cancellation is submitted only after the previous member's unbundling transaction has fully committed. A single-operation approach is strongly recommended.

 

This is expected behavior given that bundle membership is evaluated at the time of each individual update. The timing dependency is not a product defect; it arises when separate transactions overlap on the same bundle.

Número del artículo de conocimiento

005460846

 
Cargando
Salesforce Help | Article