Service Resource Not Shown in Resource List When Availability Is Beyond 31 Days

Root Cause

The Select Service Resource and Service Appointment Time component loads its resource list once, on initial screen load, scoped to only the next 31 days (up to 10 resources, sorted by availability). Navigating the calendar forward does not re-query the server for additional resources — it only filters the already-loaded list against the newly viewed dates. Resources with no availability in the first 31 days are excluded from that list entirely and will never appear, regardless of their availability later on.

This is a hard-coded, by-design limit of the standard managed component. It is not related to Work Type configuration and is not currently configurable at the org level (outside of Appointment Distribution scenarios — see Note below).

Why the Timeframe End Workaround Doesn't Work

1. Work Type > Timeframe End controls how far ahead time slots are fetched once a resource is already selected.
2. It does not change the 31-day window used to decide which resources are initially loaded into the list.
3. Increasing Timeframe End to 90 or 120 days will not surface a resource whose only availability starts after day 31.

 What To Check Service Resource Not Visible in 31-Day Window – Checklist & Fixes

1. Confirm the resource genuinely has no availability at all within the next 31 days (Operating Hours, Shifts, and Resource Absences can all affect this).
2. If the resource does have some availability within 31 days, but the list still looks wrong, verify Service Territory and Work Type/Work Type Group assignment — a resource can be filtered out for territory or skill mismatch reasons unrelated to this limitation.
3. If using Appointment Distribution, note that the resource count shown can be adjusted using the Number of Resources to Show (Appointment Distribution) attribute on the flow screen component — this does not change the 31-day discovery window, only how many of the discovered resources are shown.

Current Status

There is no supported configuration or workaround to extend the 31-day resource discovery window for this component. Attempts to work around it (increasing Timeframe End, adding assignment screens with future dates, creating Resource Absence records) do not change which resources are discovered.

Recommended Action

You can upvote this Idea :

Note: If your business process requires resources with availability beyond 31 days to be selectable, consider a custom Flow Screen built with Apex-backed resource retrieval (e.g., a custom ServiceResourcesSchedulerHandler-style lookup) instead of the standard component, since the discovery window in the standard component cannot be extended via configuration.