--- schema_version: "1" id: 5641b8f24f362bd957b525d0c43bd293a88feeace73679a579c3d670f146187f title: Appointment Bundling Limitations collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/fs_set_up_bundling_limitations.md canonical_url: https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_limitations.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 10721c6303d44bcf80ef0316dafe356849cd964908dcd94e0ecd86f447b8381b description: Review the limitations of Appointment Bundling. products: - Field Service release: "264" --- # Appointment Bundling Limitations Review the limitations of Appointment Bundling. ### Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
The Agentforce Field Service and Operations core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions.
## Aggregation Duration Downscales - When you define more than one aggregation duration downscale, they aren’t evaluated in any particular order. If your duration downscales include overlapping service appointments and include Max Reduction values, it can lead to inaccurate results. - Custom fields for service appointments used in aggregation duration downscales must have read and edit access. See [Create Appointment Bundle Aggregation Duration Downscales](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_aggregation_downscale_policy.htm&release=264.0.0&type=5 "Account for one-time tasks that are part of a bundle by downscaling the duration of the bundle member service appointments. You can create multiple aggregation duration downscales."). ## Aggregation policies - Custom fields for service appointments used in aggregation policies must have read and edit access. - For the **Allow the same value to appear more than once** option, make sure that **Do not allow duplicate values** isn’t selected in the field’s configuration settings. - For string aggregations with the Sum Based on Bundle Members action, make sure that the length of the string field can contain enough values to populate the bundle service appointment field. See [Create an Appointment Bundle Aggregation Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_aggregation_policy.htm&release=264.0.0&type=5 "Use the default aggregation policies, or create policies to determine when and how bundle member service appointments update the bundle service appointment fields. And you can create multiple aggregation policies for each bundle policy. Each aggregation policy controls how one bundle service appointment field is populated."). ## Automatic bundling Continuous bundle re-evaluation and recreation is expected behavior by design. While this ensures maximum efficiency, it may generate higher platform event volume in environments with frequent appointment changes. See [Set Up Automatic Bundling](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_automatic.htm&release=264.0.0&type=5 "Use automatic bundling to create and update bundles instead of managing them manually. Automatic bundling includes two modes: Automated Bundling and Live Bundling. The automatic bundling process looks for service appointments in a particular service territory and then looks at the priority of the bundle policy. After the bundles are created, they appear in the work list with the status None and can be scheduled."). ## Bundle Member Service Appointments related list - The Sort By option is set to Default. Other options aren’t supported. - The expanded view of the related list indicates that the appointments are sorted by due date, even if the order is determined by the Appointment Bundle Sort Policy. - Using the arrow that changes the order of the appointments according to a specific column overrides the order determined in the Appointment Bundle Sort Policy. ## Bundle policies - The Allow Scheduling Dependencies in Bundle field isn’t supported. - You can create more than one service territory policy for a bundle policy, but it isn’t recommended. The dispatcher can only bundle together service appointments with the same service territory in the same time zone. If you define more than one service territory for a bundle policy, make sure that the enhanced scheduling and optimization setting in all the service territories matches. If the setting is enabled in one service territory and disabled in another, the bundles created with the bundle policy can’t be updated. - You can delete a bundle policy even if it’s already in use. However, you can’t perform actions on a bundle that was created using that policy, such as add or remove bundle members or unbundle a bundle. - Custom fields for service appointments used in bundle policies must have read access. See [Create an Appointment Bundle Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_bundle_policy.htm&release=264.0.0&type=5 "Use the default policy, or create multiple policies. You can use the policies for manual bundling, automatic bundling, or both."). ## Experience Site users Experience Site users don’t have the Bundle Policy field in the service appointment’s Bundle tab. See [Add Permissions for Service Appointment Bundling](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_permissions.htm&release=264.0.0&type=5 "Add the permissions for service appointment bundling."). ## Localization If you change the API name of the None status after enabling Appointment Bundling, you must refresh the cache. To refresh the cache, edit and save your Bundle Config or any bundle policy. ## Optimization A scheduled path in a record-triggered flow doesn’t always work with optimization when Enhanced Scheduling and Optimization is enabled. In this case, the optimization updates are done by the platform integration user who has a session-based permission set that isn't active during the scheduled path’s execution. To grant this user the necessary permission, clone the Field Service Integration permission set, disable the Session Activation Required option, and then save. Then assign this permission set to the platform integration user. You can add more permission sets to this user if it’s necessary. ## Propagation policies Custom fields for service appointments used in aggregation policies must have read and edit access. See [Create an Appointment Bundle Propagation Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_propagation_policy.htm&release=264.0.0&type=5 "Create a policy to determine when and how the bundle service appointment updates the fields of the bundle member service appointments. And you can create multiple propagation policies for each bundle policy. Each propagation policy controls how one bundle member service appointment field is populated."). ## Recordset filter criteria Inactive recordset filter criteria aren’t supported. See [Create Recordset Filter Criteria for Bundling Appointments](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_rfc.htm&release=264.0.0&type=5 "You can create filters to bundle only the appointments that meet the criteria that you set. Creating recordset filter criteria is optional, but if you want to use them in the bundle policies, you must create them first."). ## Restriction policies Custom fields for service appointments used in sort policies must have read access. See [Create an Appointment Bundle Restriction Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_restriction_policy.htm&release=264.0.0&type=5 "Use an appointment bundle restriction policy to define restriction fields so that only service appointments with the same field values can be bundled together. Use the default policy, or create multiple restriction policies. For automatic bundling, you must have at least one restriction policy."). ## Scheduling Bundles and bundle members can't be part of a complex work chain. See [Create a Field Service Bundle Manually](https://help.salesforce.com/s/articleView?id=service.pfs_bundling_create.htm&release=264.0.0&type=5 "Create a bundle manually in the Field Service Classic Dispatch Console."). ## Service Appointments list view The Bundle Information fields from the service appointment’s details can’t be selected to display in a list view. See [Create a Field Service Bundle Manually](https://help.salesforce.com/s/articleView?id=service.pfs_bundling_create.htm&release=264.0.0&type=5 "Create a bundle manually in the Field Service Classic Dispatch Console.") and [Test Your Appointment Bundling Configuration](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_test.htm&release=264.0.0&type=5 "After completing the configuration steps for appointment bundling, test it in Field Service."). ## Sort policies Custom fields for service appointments used in sort policies must have read access. See [Create an Appointment Bundle Sort Policy](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_sort_policy.htm&release=264.0.0&type=5 "Use the default policy, or create multiple sort policies. For manual bundling, define a policy for sorting the bundle members within a bundle. The sorting is applied when bundling and unbundling service appointments. For automatic bundling, define a policy that determines the order that’s used to examine the bundling candidates."). ## Travel time - Travel time between the bundle member service appointments is also affected by the service resource’s efficiency. - When you unbundle a bundle that includes travel time, the line that indicates travel between service appointments doesn’t appear on the Gantt. See [Create an Appointment Bundle Config](https://help.salesforce.com/s/articleView?id=service.fs_set_up_bundling_bundle_config_policy.htm&release=264.0.0&type=5 "Use the default configuration, or edit it to determine the status behavior when bundling and unbundling service appointments. These configuration settings apply to all your bundles.").