---
schema_version: "1"
id: e503f53bc7f9de0b357db7fb7df70554693565a92831797001938467ca96e176
title: Test and Troubleshoot the Agent for Handling Service Resource Absences in the Legacy Agentforce Builder
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/fs_agentforce_autonomous_scheduling_resource_absence_test.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.fs_agentforce_autonomous_scheduling_resource_absence_test.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e85b99e04d4e6f46333e911d8ec8b64dd896f3b42d478b528ab2ee0389a37131
description: Now that your agent is ready to go, make sure that it’s working as expected.
products:
  - Field Service
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions with Field Service and Foundations. Also available with <strong>Einstein 1 Field Service</strong> Edition or <strong>Agentforce 1 Field Service</strong> Edition.</td></tr></tbody></table>

## 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/images/icon_note.png)
    
    Note In Slack, start the message with @Agentforce Employee Agent.
    
    ![Conversation in Slack](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_field_service-264-0-0-production-enus/3f7dceb9-dd70-454a-b49e-bbb4526a158d/support_field_service/images/agentforce_resource_absence_slack.png)
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, and exclusion rules) prevented scheduling.
    - Scheduling Policy Issues: The scheduling policy used might be missing necessary configuration.