Entry Conditions and Scheduled Paths in Record-Triggered Flows
5 minutes
5 Questions
Entry Conditions and Scheduled Paths are two powerful features in Salesforce Record-Triggered Flows that help control when and how automation runs.
Entry Conditions define the criteria a record must meet for the flow to execute. When you create a Record-Triggered Flow, you specify whether it runs …Entry Conditions and Scheduled Paths are two powerful features in Salesforce Record-Triggered Flows that help control when and how automation runs.
Entry Conditions define the criteria a record must meet for the flow to execute. When you create a Record-Triggered Flow, you specify whether it runs when a record is created, updated, or both. Entry Conditions allow you to add filters so the flow only triggers for records matching specific values. For example, you might set an Entry Condition so the flow runs only when an Opportunity's Stage equals 'Closed Won'. A key optimization option is 'Only when a record is updated to meet the condition requirements,' which ensures the flow fires as the record transitions into meeting the criteria, rather than every time it is saved while already matching. This helps prevent redundant executions and improves efficiency.
Scheduled Paths let you delay part of your flow's logic to run at a future point in time, instead of running everything the moment the record is saved. This is useful for time-based automation, such as sending a reminder email three days before a contract renewal or updating a field one hour after a Case is created. Scheduled Paths run asynchronously in the background as part of the batch scheduler. You can base the timing on a specific date/time field on the record or on a set offset before or after that field's value. You may also add conditions to Scheduled Paths so they evaluate whether the record still qualifies at execution time.
Together, these features give administrators precise, declarative control over automation timing and criteria. Entry Conditions determine which records start the flow, while Scheduled Paths determine future actions, enabling robust, efficient, and time-aware business processes built entirely with clicks rather than code.
Entry Conditions and Scheduled Paths in Record-Triggered Flows
Entry Conditions and Scheduled Paths are two of the most powerful features available in Record-Triggered Flows on the Salesforce platform. Understanding how they function is essential for any aspiring Salesforce Administrator, as they form the backbone of efficient, high-performing automation.
Why This Topic Is Important
Record-Triggered Flows run automatically when a record is created, updated, or deleted. Entry conditions and scheduled paths allow you to control precisely when a flow runs and when its actions are executed. Mastering these concepts helps you build automation that is performant, avoids recursion, and respects governor limits. On the exam, questions on this subject test your ability to choose the right configuration for a given business requirement.
What Are Entry Conditions?
Entry conditions (also called entry criteria) are the rules that a record must meet for the flow to run. When you configure a Record-Triggered Flow, you specify whether it fires:
- When a record is created - When a record is updated - When a record is created or updated - When a record is deleted
You then define conditions that filter which records trigger the flow. For example, you might only want the flow to run when an Opportunity Stage equals Closed Won. This filtering keeps your flow from executing unnecessarily on records that do not matter.
The 'Only when a record is updated to meet the condition requirements' Option
A key setting for update-based flows is the option that limits execution to records that newly meet the criteria. When selected, the flow runs only if the record did not satisfy the conditions before the update but does after. This prevents the flow from re-running on records that already met the conditions, which is a common source of unwanted repeated execution.
What Are Scheduled Paths?
Scheduled paths let you delay actions to a future point in time, rather than executing everything the moment the flow is triggered. A scheduled path runs asynchronously and can be based on:
- A set time after the record is created or updated (for example, 3 days after) - A set time before a date/time field value (for example, 2 days before a Close Date) - A time relative to a specific field on the record
Scheduled paths are ideal for use cases such as sending reminder emails, escalating stale cases, or performing follow-up actions on a schedule.
How It Works
When a record triggers the flow and meets the entry conditions, the immediate path (called the Run Immediately path) executes at once. Any configured scheduled paths are then queued to run at the calculated future time.
Before a scheduled path executes, Salesforce re-evaluates the entry conditions to confirm the record still qualifies. If the record no longer meets the criteria, the scheduled path is skipped. This built-in check ensures your delayed actions remain relevant.
Scheduled paths execute in the context of the Automated Process user, which is worth remembering when troubleshooting field access or ownership behavior.
How to Answer Exam Questions
Exam questions often present a business scenario and ask you to select the correct configuration. To answer well:
1. Identify the trigger event (create, update, delete). 2. Determine whether the requirement involves an action happening now or at a later time. A future timing requirement points to a scheduled path. 3. Watch for language such as 'only when the record newly meets' the criteria, which signals the option limiting execution to records changed to meet the requirements. 4. Remember that scheduled paths re-check entry conditions before running.
Exam Tips: Answering Questions on Entry Conditions and Scheduled Paths in Record-Triggered Flows
- Match timing keywords: Phrases like 'after 24 hours', 'two days before', or 'next day' almost always indicate a scheduled path is the answer. - Understand re-evaluation: Know that Salesforce checks entry conditions again before a scheduled path fires, so records that changed may skip the scheduled action. - Recognize the update option: If a scenario mentions running a flow only the first time a condition becomes true, choose the setting that runs the flow only when a record is updated to meet the requirements. - Consider performance: Well-defined entry conditions reduce unnecessary flow runs and help respect governor limits, which is often the correct reasoning in 'best practice' style questions. - Know the running user: Scheduled paths run as the Automated Process system user, which can affect record visibility and field updates. - Eliminate wrong answers: Rule out options that suggest using an apex trigger or another tool when a scheduled path can meet the requirement declaratively.
By keeping these principles in mind, you will be able to confidently choose the correct answers on questions involving entry conditions and scheduled paths.
