You can define rules that trigger time-based workflow actions off any Date or Date Time field on an object.
Example of time-based workflow: Generate critical date reminders to remind Opportunity owners when a large Opportunity (amount greater than $1M USD) is 14 days away from the intended Close Date. Use the same rule to notify the executive sponsor and change the ownership of the Opportunity if the Close Date is just 10 days away.
Here's our top questions, tips, and considerations:
This feature leverages the existing Workflow engine, which includes two sections: Immediate actions and Time-dependent actions.
The basic rule configuration is the same, but for time-based rules, you configure time-triggers in the Time-dependent actions section. Each time trigger can execute one or more Workflow actions. Please review Add Automated Actions to Your Workflow Rule.
Yes, and on any object currently supported by Workflow.
Currently, days and hours are supported.
Standard functionality is based on all days and cannot exclude weekends.
Workflow rules are not triggered retroactively. If you create a rule now, the rules are not applied to previously created records.
All existing actions will be available: Email Alerts, Field Updates, Tasks, and Outbound Messages.
Yes, you can create a timeline of actions by configuring multiple time triggers and defining actions for each one.
Yes, it's not possible to configure a time-dependent workflow action that's set to evaluate criteria "Every time a record is created or edited."
Yes, all pending actions to be triggered on a future date appear in the Workflow Queue. See Monitor Pending Workflow Actions.
System Administrators can view and manage the queue from:
Classic
Lightning
No. Time-dependent actions remain in the Workflow Queue until processed or the rule criteria for the Workflow Rule are evaluated as "false." If a record no longer matches the rule criteria when the rule is evaluated, Salesforce removes the time-dependent actions queued for that record.
Yes, if the record is updated and you set the evaluation criteria to be "When a record is created, and anytime it's edited to subsequently meet criteria" (The record should not have previously met the entry criteria).
In this case, the Workflow rule evaluates the time triggers only once. If the record that fired the rule changes and no longer meets the evaluation criteria, the pending actions are removed from the queue and the rule is never reapplied to the record.
All pending actions are evaluated only for as long as the rule criteria is true. While Salesforce evaluates the rule every time the record is updated, it does not trigger all the actions associated with the rule every time.
Salesforce recalculates the time trigger as long as the time trigger has not yet fired and the recalculation does not reschedule the time trigger to a date in the past.
The pending actions are deleted from the Workflow Queue and cannot be restored, even if you undelete the record.
If there are any pending Approval Processes or Workflows to be triggered, you will not be able to convert a Lead. That said, you can remove the pending actions under Setup and the conversion will go through.
Learn more in the "Time Trigger Processing" section of Considerations for Time-Dependent Actions and Time Triggers.
Get the full set of instructions in our Retroactively trigger workflow on current records help article.
This is standard behavior. Time based workflow actions will not always execute at the exact time displayed in the Monitoring setup menu. Please review Time Based Workflow Execution interval is 15 minutes.
000385301

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.