You are here:
Set Up Dynamic Due Dates in Agentforce Operations
Configure a blueprint to automatically shift downstream task due dates when upstream tasks complete late or early in Agentforce Operations.
You are here:
Configure a blueprint to automatically shift downstream task due dates when upstream tasks complete late or early in Agentforce Operations.
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
| Role or Access Needed | |
|---|---|
| To create a blueprint from scratch, using AI, or by importing a .rex file in Agentforce Operations: | Admin role or Creator role |
To create a blueprint by importing a .docx file in Agentforce Operations: |
Admin role |
| To publish a blueprint in Agentforce Operations: | Admin role or Publisher role with View access for the blueprint |
| To edit a blueprint in Agentforce Operations: | Admin role, Creator role, or a user with Edit access for the blueprint |
When dynamic due dates are on, Agentforce Operations recalculates downstream task due dates whenever an upstream task completes late or early. The relative time windows between tasks stay the same. For example, if a task completes two days late and the next task has a three-day window, that task's due date moves forward two days.
When dynamic due dates are off, all task due dates are fixed from the moment the workflow starts and don't adjust based on actual completion times.
Use dynamic due dates when tasks depend on each other sequentially and you expect some schedule changes. Don't use dynamic due dates when downstream tasks have hard calendar deadlines that you want to keep from moving.
Dynamic due dates affect when escalations trigger. If a task due date shifts, Agentforce Operations recalculates escalation times accordingly. For details, see Task Escalation Limits and Considerations in Agentforce Operations.

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.