---
schema_version: "1"
id: da5b287c44af0a15ad07667d76548a63186640361b41f9f8662fdefa840f21df
title: Set Up Dynamic Due Dates in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_dynamic_due_dates.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_dynamic_due_dates.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d0b20eeb82652a9821cbc8b5e24ddcbd75b7e417ab8233f789d5c5da09482b16
description: Configure a blueprint to automatically shift downstream task due dates when upstream tasks complete late or early in Agentforce Operations.
products:
  - Cross Cloud
release: "264"
---
# 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.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d20480e39">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e39 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d20480e73">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">To create a blueprint from scratch, using AI, or by importing a .rex file in
              Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">Admin role or Creator role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">
              <p style="margin-bottom:0;">To create a blueprint by importing a .docx file in Agentforce Operations:</p>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">To publish a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">Admin role or Publisher role with View access for the blueprint</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">To edit a blueprint in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d20480e73 ">Admin role, Creator role, or a user with Edit access for the blueprint</td>

          </tr>
        </tbody>
      </table>

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.

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the blueprint, click the **Settings** tab.
3. In the **Dynamic due dates** section, click **Set up**.
4. Select **Dynamic due dates.**
5. Click **Save**.

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](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_task_escalations_considerations.htm&release=264.0.0&type=5 "Review limits and considerations for task escalations in Agentforce Operations.").