---
schema_version: "1"
id: d1ae5492935a6a2db3e77fa0594b1605dca18e8a9996e1e2985b8eab7085a78e
title: Troubleshoot Workforce Availability in Emergency Management
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/energy_troubleshoot_workforce_availability_in_emergency_management.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.energy_troubleshoot_workforce_availability_in_emergency_management.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ce447d45810198d1051943fff7a5d9b0e0925230b4dc74db1b9e06dda92571c5
description: When the available resource count on a callout requirement is zero or blank, use these checks to find why Field Service returns no eligible resources.
products:
  - Energy and Utilities
release: "264"
---
# Troubleshoot Workforce Availability in Emergency Management

When the available resource count on a callout requirement is zero or blank, use these checks to find why Field Service returns no eligible resources.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></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>, and <strong>Unlimited</strong> editions with Energy &amp; Utilities - Growth, Field Service for Energy &amp; Utilities, and Contractors for Energy &amp; Utilities</td></tr></tbody></table>

After you create a resource callout, the callout process generates a resource callout requirement record for each pay grade and populates its available resource count. When that count is 0 or null, dispatchers can't build a usable roster. The cause is different for a null count than for a zero count, so start by checking which one you see.

- **[When the Available Resource Count Is Null](https://help.salesforce.com/s/articleView?id=ind.energy_when_the_available_resource_count_is_null.htm&release=264.0.0&type=5)**  
    A null count means that the availability step didn't run or didn't write back to the requirement record.
- **[When the Available Resource Count Is Zero](https://help.salesforce.com/s/articleView?id=ind.energy_when_the_available_resource_count_is_zero.htm&release=264.0.0&type=5)**  
    A zero count means that the flow ran, but Field Service found no resources that satisfy the scheduling policy. The callout process uses a scheduling policy named Emergency, which is made up of work rules and goals defined in the Field Service managed package. Verify that the service appointment linked to your resource callout satisfies the policy's work rules, and that resources are members of the same service territory.
- **[Work Rules in the Emergency Scheduling Policy](https://help.salesforce.com/s/articleView?id=ind.energy_work_rules_in_the_emergency_scheduling_policy.htm&release=264.0.0&type=5)**  
    Work rules are hard constraints. A resource must satisfy every rule to be considered available.
- **[Goals in the Emergency Scheduling Policy](https://help.salesforce.com/s/articleView?id=ind.energy_goals_in_the_emergency_scheduling_policy.htm&release=264.0.0&type=5)**  
    Goals are soft constraints that influence ranking. They don't eliminate candidates. The Emergency policy uses one goal, ASAP, which prefers the earliest available time slot. Among resources with equal availability, the ASAP goal uses a Least Qualified strategy with the priority field to deprioritize the most qualified resources, which preserves them for higher-complexity jobs.
- **[Additional Availability Checks the Engine Makes](https://help.salesforce.com/s/articleView?id=ind.energy_additional_availability_checks_the_engine_makes.htm&release=264.0.0&type=5)**  
    Beyond the explicit work rules and goals, the Field Service GradeSlotsService engine applies these implicit checks.