PranavNagrecha/AwesomeSalesforceSkills / skills/admin/fsl-scheduling-policies
fsl-scheduling-policies
VerifiedUse this skill to create, configure, or tune Field Service Lightning scheduling policies — including work rules (pass/fail filters) and service objectives (weighted ranking criteria). Covers the four default policies, custom policy design, work rule type selection, and objective weighting strategy. NOT for running or tuning the Optimizer itself — use admin/fsl-scheduling-optimization-design. NOT for resource skills and preferences — use admin/fsl-resource-management. NOT for resource capacity records — use admin/fsl-capacity-planning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.4 KB |
| references/examples.md | markdown | 4.9 KB |
| references/gotchas.md | markdown | 5.6 KB |
| references/llm-anti-patterns.md | markdown | 6.9 KB |
| references/well-architected.md | markdown | 4.9 KB |
| scripts/check_fsl_scheduling_policies.pyexecutable | script | 8.2 KB |
| templates/fsl-scheduling-policies-template.md | markdown | 3.5 KB |
references/gotchas.md
View on GitHub# Gotchas — FSL Scheduling Policies
Non-obvious Salesforce platform behaviors that cause real production problems in this domain.
## Gotcha 1: Missing Service Resource Availability Rule Silently Ignores All Absences and Working Hours
**What happens:** If a custom scheduling policy does not include the Service Resource Availability work rule, the scheduling engine treats every time slot as available for every resource, regardless of the resource's configured working hours, operating hours, and absence records. Technicians get scheduled during lunch breaks, on their days off, during approved vacation, and outside their shift windows. No error or warning is displayed anywhere in the UI or logs.
**When it occurs:** Any custom policy built from scratch or cloned from a base that had the rule removed. This is particularly common when administrators build a lightweight "test" policy and forget to add the rule, then deploy it to production.
**How to avoid:** Treat Service Resource Availability as a mandatory baseline rule in every policy. The check script in this skill's scripts directory validates for its presence. After any policy configuration change, verify the rule list explicitly — do not assume the clone retained it.
---
## Gotcha 2: Gantt Yellow Triangle Is Informational Only — Dispatch Proceeds Regardless
**What happens:** When a dispatcher manually assigns a service appointment that violates one or more work rules in the active policy, the Gantt view displays a yellow warning triangle on the appointment block. Many practitioners interpret this as a blocking validation error and believe the appointment has not been saved. The appointment is, in fact, saved and the resource is dispatched. The violation is recorded but not enforced.
**When it occurs:** Any manual drag-and-drop or direct assignment in the Dispatcher Console when the chosen slot violates a work rule (e.g., the technician lacks the required skill, or the appointment is outside operating hours). It also occurs during bulk optimization when the optimizer is configured to allow violations.
**How to avoid:** Train dispatchers that yellow triangles are warnings, not errors. If policy violations must be prevented, consider implementing a before-save Apex trigger or validation rule on ServiceAppointment to block saves where critical work rules are violated. Alternatively, audit yellow triangle rates in a custom report to identify dispatchers routinely overriding policy.
---
## Gotcha 3: Service Objective Weights Do Not Enforce a 100% Sum — Imbalanced Weights Produce Unpredictable Rankings
**What happens:** Salesforce does not validate that the percentage weights of service objectives within a policy sum to 100%. A policy can have three objectives weighted at 10%, 10%, and 10% (total 30%) and will save without error. The scheduling engine normalizes the weights internally, but the resulting behavior differs from what a practitioner intending 33%/33%/33% would expect. Similarly, weights summing to 200% are accepted.
**When it occurs:** Whenever objectives are added, removed, or reweighted without manually recalculating the total. This is especially common after an objective is removed and the remaining weights are not redistributed.
**How to avoid:** After any change to service objective weights, manually sum all active objective percentages and confirm they total 100%. Document the intended weights in a configuration record or a notes field on the policy. The check script in this skill validates objective weight totals.
---
## Gotcha 4: Work Rule Ordering Within a Policy Has No Effect
**What happens:** The list of work rules in a scheduling policy can be reordered via drag-and-drop in the UI. Practitioners familiar with firewall rules, conditional logic, or ordered filter chains expect earlier work rules to apply first. FSL applies all work rules in a policy simultaneously as a set — not sequentially. Reordering work rules changes only the display order, not the filtering logic or outcome.
**When it occurs:** When troubleshooting unexpected scheduling results, administrators often reorder rules trying to "prioritize" a specific filter. The reordering has no observable effect, leading to confusion about why the behavior did not change.
**How to avoid:** Understand that all work rules in a policy are evaluated as a single combined filter gate. To prioritize or deprioritize filtering behavior across different use cases, use separate policies — not rule ordering within a single policy.
---
## Gotcha 5: Default Policies Are Not Write-Protected — Edits Affect All Territories Using Them
**What happens:** Salesforce prevents deletion of the four default policies but does not prevent in-place edits to their work rules or objective weights. An edit to the Customer First policy immediately propagates to every service territory configured to use it as its default scheduling policy. There is no draft/publish mechanism, no change tracking in standard audit fields, and no warning that other territories are affected.
**When it occurs:** During initial setup or troubleshooting, when administrators experiment with settings on what they assume is a safe default object. It also occurs during upgrades if a sandbox refresh carries the modified default into a new environment.
**How to avoid:** Never edit default policies in place. Clone them before making any changes, name the clone descriptively, and assign territories to the clone. Treat the four defaults as read-only reference implementations. Periodically audit default policy configurations against the Salesforce documentation to detect accidental drift.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |