scheduled-path-patterns
Scheduled Paths in record-triggered Flow: delayed execution, time-offset from field, batch size tuning, monitoring Paused Flow Interviews, async limits. NOT for Scheduled Flow (use scheduled-flow-patterns). NOT for time-based workflow rules (use migrate-workflow-pb).
Best use case
scheduled-path-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Scheduled Paths in record-triggered Flow: delayed execution, time-offset from field, batch size tuning, monitoring Paused Flow Interviews, async limits. NOT for Scheduled Flow (use scheduled-flow-patterns). NOT for time-based workflow rules (use migrate-workflow-pb).
Teams using scheduled-path-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scheduled-path-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scheduled-path-patterns Compares
| Feature / Agent | scheduled-path-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Scheduled Paths in record-triggered Flow: delayed execution, time-offset from field, batch size tuning, monitoring Paused Flow Interviews, async limits. NOT for Scheduled Flow (use scheduled-flow-patterns). NOT for time-based workflow rules (use migrate-workflow-pb).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Scheduled Path Patterns Activate when designing a record-triggered Flow with delayed execution — "after 1 hour," "1 day before Close Date," "every Monday at 9 AM after creation." Scheduled Paths replace many time-based workflow rule use cases but have their own batching, monitoring, and failure semantics. ## Before Starting - **Understand the offset anchor.** Scheduled Paths offset from either the record-triggered event time OR a field value on the record. - **Plan for volume.** Scheduled Paths queue paused Flow Interviews; bulk inserts create bulk paused interviews with batch-size tuning. - **Know the monitoring surface.** Setup → Paused Flow Interviews shows queued interviews; failures surface in the Flow debug log and Apex exception email. ## Core Concepts ### Offset types - **From the trigger event**: "1 hour after record is created" - **From a field value**: "3 days before CloseDate" — uses a datetime/date field on the record ### Batch size Salesforce processes paused interviews in batches (default 200, tunable in Process Automation settings). Batching controls governor limits for the collection of resumed flows. ### Paused Flow Interview When a Flow hits a Scheduled Path wait, it suspends as a Paused Flow Interview. The interview resumes at the scheduled time. Monitor at Setup → Paused Flow Interviews. ### Execution context Scheduled path execution runs in system context by default (like other record-triggered Flow), with its own governor limit scope. Updates to records made in the scheduled branch are separate transactions from the trigger. ## Common Patterns ### Pattern: Follow-up reminder 24 hours after creation Record-Triggered Flow on Case Create → Scheduled Path 1 day after creation → Check IsClosed → If open, send notification to owner. ### Pattern: Pre-renewal email 30 days before renewal date Trigger on Contract update → Scheduled Path 30 days before `RenewalDate__c` → Send email alert. ### Pattern: Re-check condition at path execution Always re-query record state in the scheduled branch. The record may have changed between queue-time and execution-time. ## Decision Guidance | Need | Mechanism | |---|---| | Run N hours/days after record event | Scheduled Path | | Run at an absolute time (9 AM Monday) | Scheduled Flow or cron | | Run when a field value changes | Record-triggered Flow (no scheduled path) | | Delayed re-check of async state | Scheduled Path + re-query | | High-volume time-based fan-out | Apex Schedulable + Queueable | ## Recommended Workflow 1. Identify the offset anchor: event time vs field value. 2. Define the exact offset (units: minutes, hours, days). 3. Add explicit filter criteria to the path entry — avoid queuing millions of no-op interviews. 4. In the scheduled branch, re-query or re-check the record's current state. 5. Tune Process Automation batch size for your volume. 6. Monitor Paused Flow Interviews in Setup; handle failures via admin email. 7. Test with a bulk insert to confirm batch behavior. ## Review Checklist - [ ] Offset type explicit (event vs field) - [ ] Entry criteria scoped tightly (no "always queue") - [ ] Scheduled branch re-checks current record state - [ ] Batch size reviewed for volume profile - [ ] Paused Flow Interview monitoring documented - [ ] Admin notification on scheduled-path errors enabled - [ ] Bulk insert test confirms expected behavior ## Salesforce-Specific Gotchas 1. **Deleting the triggering record deletes its paused interview.** The scheduled branch never runs for deleted records. 2. **Changing the source field after the path is scheduled does NOT reschedule.** The scheduled time is computed once at entry. 3. **Flow version updates do not migrate paused interviews.** Queued interviews execute under the version that queued them; test version swaps carefully. ## Output Artifacts | Artifact | Description | |---|---| | Scheduled Path design | Offset anchor, filter, re-check logic | | Monitoring runbook | Where to check Paused Flow Interviews + error emails | | Volume test plan | Bulk insert → expected queued count | ## Related Skills - `flow/scheduled-flow-patterns` — absolute-time scheduled flows - `admin/migrate-workflow-pb` — replacing time-based workflow rules - `apex/apex-queueable-patterns` — programmatic async alternatives
Related Skills
mfa-enforcement-patterns
Design MFA enforcement: auto-enablement, Salesforce Authenticator rollout, exceptions, service accounts, API-only users, SSO interop, and audit. Trigger keywords: MFA, multi-factor, two-factor, Salesforce Authenticator, MFA exception, MFA SSO, api-only MFA. Does NOT cover: end-user password policies, device-trust posture, or non-Salesforce IdP configuration.
encrypted-field-query-patterns
Design SOQL, filters, reporting, and indexes against Shield Platform Encryption fields. Trigger keywords: Shield Platform Encryption, encrypted field query, probabilistic vs deterministic encryption, encrypted SOQL filter, encrypted field index. Does NOT cover: Classic Encryption (deprecated), field-level security policy, or tenant secret key rotation.
apex-managed-sharing-patterns
Grant row-level access programmatically via __Share records when declarative sharing rules cannot express the policy. NOT for OWD, role hierarchy, or criteria-based sharing rule design.
omnistudio-testing-patterns
Use when testing or validating OmniStudio components — OmniScript preview, Integration Procedure step debugging, DataRaptor field-mapping validation, and end-to-end UTAM-based automation. NOT for Apex unit testing or standard Flow debugging.
omnistudio-error-handling-patterns
Use when designing fault behavior across Integration Procedures, DataRaptors, OmniScripts, and FlexCards — error routing, user-facing messaging, retry semantics, and idempotency. Triggers: 'omnistudio error', 'integration procedure fault', 'dataraptor error handling', 'omniscript retry', 'flexcard action failure'. NOT for general Apex exception design or Flow fault paths.
omnistudio-ci-cd-patterns
Use when designing or implementing CI/CD pipelines for OmniStudio components — DataPack export/import, versioning, environment promotion, and automated deployment. NOT for standard Salesforce metadata CI/CD or Apex-only pipelines.
omniscript-design-patterns
Use when designing or reviewing OmniScripts for guided experiences, step structure, branching, save/resume, and the boundary between OmniScript, Integration Procedures, DataRaptors, and custom LWCs. Triggers: 'omniscript design', 'too many steps in omniscript', 'save and resume omniscript', 'branching in omniscript', 'when should this be an integration procedure'. NOT for deep Integration Procedure or DataRaptor design when the guided interaction layer is not the main concern.
integration-procedure-cacheable-patterns
Use when designing Integration Procedures (IPs) with platform cache to cut latency and callout load. Covers cache key design, TTL selection, per-user vs org-wide partitions, invalidation on data changes, and safe fallback on cache miss/stale. Does NOT cover general IP authoring (see omnistudio-error-handling-patterns) or LWC client-side caching.
flexcard-design-patterns
Use when designing, building, or reviewing OmniStudio FlexCards — including data source selection, card states, actions, conditional visibility, flyout configuration, and child card iteration. Triggers: 'FlexCard', 'card template', 'flyout', 'card action', 'card state', 'data source', 'child card', 'conditional visibility'. NOT for OmniScript design, standalone LWC development, or Apex controller architecture outside the FlexCard context.
dataraptor-patterns
Use when designing or reviewing OmniStudio DataRaptors, especially Extract versus Turbo Extract versus Transform versus Load, field mapping strategy, performance tradeoffs, and when to move work into Integration Procedures or Apex. Triggers: 'DataRaptor Extract', 'Turbo Extract', 'DataRaptor Load', 'DataRaptor Transform', 'OmniStudio data mapping'. NOT for overall OmniScript journey design or Integration Procedure sequencing when the main question is not the DataRaptor shape itself.
wire-service-patterns
Use when designing or reviewing Lightning Web Components that use `@wire`, Lightning Data Service, UI API, or the GraphQL wire adapter, especially for reactive parameters, cache behavior, and refresh strategy. Triggers: 'wire service', 'refreshApex', 'reactive parameter', 'getRecord', 'wire vs imperative Apex'. NOT for component communication or generic lifecycle issues when data provisioning is not the main concern.
message-channel-patterns
Use when implementing Lightning Message Service (LMS) to enable cross-DOM communication between LWC, Aura, and Visualforce components on the same Lightning page, using message channels. Triggers: 'communicate between unrelated LWC components', 'send data between Visualforce and LWC', 'lightning message service not working', 'APPLICATION_SCOPE vs default scope', 'message channel metadata deployment'. NOT for parent-child component communication (use component-communication) or server-side events.