Loading

No Slots Found Using the Salesforce Field Service Book Appointment Quick Action

Fecha de publicación: Jun 1, 2026
Descripción

In Salesforce Field Service (FSL), when using the Book Appointment Quick Action on a Service Appointment (or Work Order), dispatchers or admins may see the message: 'No slots were found.' This is not an error — it means the scheduling engine evaluated all available Service Resources but could not find any that satisfy the configured Work Rules in the active Scheduling Policy for this appointment. The steps below describe how to identify which Work Rule is causing the appointment to go unscheduled.

Solución

When receiving the Field Service message that "No slots were found", perform the following to troubleshoot the issue:

1. Identify a Service Resource who has available slots for the Service Appointment in question.

"Note: If using the Book Appointment action on a record that is not a Service Appointment, create a child test Service Appointment before proceeding." test Service Appointment before proceeding.

2. Identify what Scheduling Policy is being used by the quick action:


a. Go to the Field Service Settings tab | Global Actions | Appointment Booking
b. Take note of the policy that is currently selected for Default scheduling policy


3. Navigate to the Dispatcher Console (also known as the Field Service tab).
4. Set the Policy to the Scheduling Policy you took note of in step 2.
5. Drag the affected Service Appointment from the Service Appointment list to the Gantt row for the identified Service Resource from step 1.
6. Hover over the Service Appointment.

The list of violated Work Rules will be shown under the Rule Violations section of the tool-tip.

Número del artículo de conocimiento

000383445

 
Cargando
Salesforce Help | Article