Past Due Notifications
Scenario
A workflow step is past due if the assignee misses the due date or their access to the Directory tool was removed while the workflow step was active. This immediately stops the workflow, and the system sends a past due notification.
ExampleBecause Person A, a required approver, was removed from the Directory tool during the approval step, the workflow is stuck and will become past due.
Because Person A, a required approver, was removed from the Directory tool during the approval step, the workflow is stuck and will become past due.
Impact
The workflow remains stuck until the assignment problem is fixed
Past due notifications alert the workflow manager, who then takes action.
TipWhat about future workflows? If an assignee lacks proper permissions or loses Directory tool access when a workflow is running,the workflow template's assignee becomes invalid or ineligible for assignment. If this happens after a workflow starts, only the ongoing workflows are affected.
Resolution
To resolve this challenge, a workflow manager can:
Reassign Assignee: In the specific workflow, use the side panel or the bulk edit tool to assign the step to someone else who has the correct access.
Remove Role Requirement: If the assignee's input isn't needed anymore, the workflow manager can remove the requirement for that role.
Non-Required Responders: If the assignee is a required responder for the step (e.g., the step was configured with "First Responder Decides"), the workflow keeps going without interruption, and no past due notification is sent.