Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Agentforce Field Service and Operations
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Test and Troubleshoot the Agent for Handling Service Resource Absences in the Legacy Agentforce Builder

          Test and Troubleshoot the Agent for Handling Service Resource Absences in the Legacy Agentforce Builder

          Now that your agent is ready to go, make sure that it’s working as expected.

          Required Editions

          Available in: Lightning Experience
          Available in: Enterprise, Performance, Unlimited, and Developer Editions with Field Service and Foundations, or Einstein 1 Field Service Edition or Agentforce 1 Field Service Edition.

          Test the Agent

          1. From Field Service, find a service resource who has multiple service appointments.
          2. In Slack or in the Field Service mobile app, write: I’m sick today. Note: In Slack, start the message with @Agentforce Employee Agent.
            Note
            Note In Slack, start the message with @Agentforce Employee Agent.
            Conversation in Slack
          3. View the created Resource Absence on the Gantt and pay attention to the appointments that were rescheduled successfully.
          4. For appointments that couldn’t be rescheduled, a Customer Outreach message is sent to the customer for rebooking purposes. In the meantime, these appointments remain assigned to the service resource.

          Troubleshoot the Agent

          To see why certain service appointments weren’t rescheduled with this process, use Flow Builder to see what caused the failure. Modify your setup as required.

          1. In Setup, find and select Flows.
          2. Find and select the Reschedule Service Appointment flow.
          3. In Flow Builder, click Debug.
          4. When prompted for the serviceAppointmentId input variable, enter the ID of one of the service appointments that failed to reschedule.
          5. Analyze the output. Running the flow directly with the specific service appointment ID in debug mode can reveal critical information, such as:
            • No Candidate Slots Found: The scheduling policy couldn’t find a suitable time or service resource.
            • Scheduling Constraints Violation: Specific rules (for example, skill requirements, travel time, operating hours, exclusion rules) prevented scheduling.
            • Scheduling Policy Issues: The scheduling policy used might be missing necessary configuration.
           
          Loading
          Salesforce Help | Article