Check Rule Violations on the Field Service Gantt

This is a Field Service managed package feature.

Right-click one or more appointments on the Gantt chart or list and click Check Rules to manually check rule violations for selected service appointments. To manually check rules on demand for all loaded services on the Gantt, click Check Rules next to the scheduling policy.

The scheduling policy selected at the top of the appointment list controls which rules are applied. If a rule violation occurs, the service appointment appears on the Gantt with a yellow triangle. Hover over the appointment to view its details and violated rules.

When optimizing your team’s or a service resource’s schedule, appointments with rule violations remain pinned. With Enhanced Scheduling and Optimization, the optimization engine tries to fix rule violations to improve the schedule by rescheduling or unscheduling rule violating appointments. To keep these appointments scheduled as is on the Gantt, the service appointments must first be pinned or in a pinned status.

Use the Check Rules feature to bulk-validate service appointments on the Gantt against your scheduling policy work rules and display rule violations. This feature is applicable only if your Rule Validation Frequency field in Field Service Settings isn’t set to Always. Always is the default setting for Salesforce orgs created before Summer ’21, where rules are checked for violations on all scheduled services after every operation.

When you click the Check Rules button next to the scheduling policy, the system validates up to 6,000 service appointments on the Gantt against your work rules and checks for violations. If you receive a notification that not all appointments were validated against your policy rules, try to load fewer service appointments by shortening the horizon or viewing fewer service territories. Then perform the check again to ensure all appointments are validated.

Note When a bulk check rules operation is run, the service appointment records on the dispatcher console Gantt are checked for rule violations in batches. Each batch size can be up to 200 service appointments. However, if a batch has more than 40 assigned resources or spans over more than seven days, it’s split into multiple batches. The more fragmented the service appointments are over time and resources, the more batches are needed. For example, 80 service resources each with one assigned appointment on the same date results in two batches. A single resource with 12 service appointments each scheduled on the first day of each month results in 12 batches, each with a single service resource. The system processes up to 30 batches of service appointments during each check rules operation. The maximum number of appointments that can be validated against work rules in one check rules operation is calculated as 200 records per batch × 30 batches = 6,000 records. However, if fewer service appointments are found for the first 40 resources across the first 7 days of the Gantt horizon (for example, 100), that number is used for the batches. This option results in fewer records processed (100 records per batch × 30 batches = 3,000 records).

Note Too many work rules in a scheduling policy can result in an Apex CPU timeout when checking rules for a large number of service appointments. If you experience a timeout when checking rules, try removing some work rules, or check rules for fewer service appointments.

When automatic scheduling is used—with the Schedule or Candidates action—rule violations don’t occur. Field Service automatically formulates schedules that don’t violate rules, so rule violations occur only as a result of manual scheduling.