Blocked Workflows
Scenario
A workflow stops if a step begins without available or eligible assignees. This happens if:
An administrator removes the workflow assignee(s) user profile from the Directory tool or changes the assignee's access or permissions before the workflow reaches the impacted step.
The workflow step is assigned to a role (like an invoice contact) in Procore, but the 'Invoice Contact' field is empty on the contract.
ExampleWhen using a workflow to approve an invoice, the 'Invoice Contact' role must be assigned to an eligible user on the invoice's contract. If no one is assigned this role when the invoice workflow reaches this step, the workflow stops.
When using a workflow to approve an invoice, the 'Invoice Contact' role must be assigned to an eligible user on the invoice's contract. If no one is assigned this role when the invoice workflow reaches this step, the workflow stops.
Impact
The workflow immediately stops.
An Assignment Required error message appears, accompanied by a Continue button.
The workflow template becomes temporarily unavailable until the issue causing the blocked instance is addressed.
Resolution
To resolve this challenge, a workflow manager can:
Reassign Assignee: Use the specific workflow instance's side panel or edit with the bulk assign feature to reassign a valid individual to the required step.
Remove Step Requirement: If the step is no longer necessary, the workflow manager can remove the requirement for the affected step.
Retry Assignment: If someone changed an assignee's Directory tool access or their permissions recently, click Continue to find available assignees for that step.