Quote management approval workflow automation stuck at manager review step

ERP Microsoft Dynamics 365
, , , , , , ,
1

Our sales quote approval workflow is consistently halting at the manager review step for quotes exceeding $50K. The workflow shows status “In Progress” but the approval task never reaches the assigned manager’s work item queue.

I’ve verified the manager has the correct security role (Sales Manager) and workflow permissions are configured properly. The workflow transition conditions check quote amount and customer credit status before routing to management approval. Notification emails are being sent, but the actual work item doesn’t appear in the manager’s action center.

When I check the workflow history, it shows the task was assigned but there’s no subsequent action logged. Has anyone encountered workflow task delegation issues where the assignment completes but the work item visibility fails? We’ve had 23 quotes stuck in this state over the past two weeks causing significant approval delays.

system 2

Excellent troubleshooting! Let me provide a complete solution covering all the workflow routing aspects:

1. Workflow Transition Conditions: Your approval step transition conditions must be properly configured to evaluate before task assignment. In the workflow designer, verify the manager approval element has conditions like:

  • Quote amount > $50,000
  • Customer credit status = Approved
  • Quote status = Submitted

These conditions should be in the “Condition” tab of the approval element, not in the step configuration. If conditions are misplaced, the workflow creates tasks but routing logic fails.

2. Task Delegation Rules: Completely remove old delegation rules rather than deactivating them:

  • Navigate to System Administration > Setup > Workflow > Delegation
  • Filter by the manager’s user ID
  • Delete any historical delegations (even if marked inactive)
  • Verify no conflicting delegations exist for the same date ranges

Delegation rules override direct assignments, so clean configuration is critical.

3. Role-Based Security Configuration: The workflow system account needs specific privileges to create work items for target users:

Required privileges for Sales Manager role:

  • Maintain work items (WorkflowWorkItemMaintain)
  • View work items (WorkflowWorkItemView)
  • Execute workflow (WorkflowExecute)

Grant these to the workflow system account:


System Administration > Security > Security configuration
→ Roles: Workflow service account role
→ Duties: Add "Maintain workflow work items" duty

Without these privileges, task assignment completes but work item creation fails silently.

4. Notification Configuration: Notifications are independent of task routing. Verify both are configured:

In workflow element properties:

  • Assignment tab: Set to “Participant” → “Manager” (hierarchy-based)
  • Notifications tab: Enable “Assignment” notification
  • Template: Select appropriate email template

Validate notification recipients: Test notifications separately from task assignment to isolate issues. If emails arrive but tasks don’t, it’s always a security or hierarchy problem.

5. Worker Hierarchy Validation: Even with correct security, Worker hierarchy must be properly configured:

  • Navigate to Human Resources > Workers > Positions > Position hierarchy
  • Verify manager’s position is correctly placed in the organizational hierarchy
  • Confirm the workflow uses the same hierarchy type (Organization hierarchy vs. Position hierarchy)
  • Check that the hierarchy is set as “Workflow” purpose-enabled

6. Workflow History Diagnostics: For future troubleshooting, always check detailed execution logs:


System Administration > Inquiries > Workflow > Workflow history
→ Select stuck workflow instance
→ Click "Tracking details" button
→ Review each workflow element execution
→ Look for errors/warnings in the message log

Security-related failures often only appear in tracking details, not in the main status view.

7. Testing Protocol: After applying fixes:

  1. Create a test quote under $50K (should bypass manager approval) - verify it completes
  2. Create a test quote over $50K with approved customer - verify it routes to manager
  3. Have manager check Action Center for work item visibility
  4. Test notification delivery separately
  5. Monitor workflow history for any new errors

Resolution for Your Specific Issue: The root cause was missing “Maintain work items” privilege on the workflow system account for the Sales Manager role. This allowed task assignment to complete (triggering notifications) but prevented actual work item creation in the manager’s queue.

After adding the privilege, your 23 stuck quotes should be retrievable by resubmitting them through the workflow (recall and resubmit). They won’t automatically resume from the stuck state.

Prevention: Implement workflow monitoring alerts that trigger when tasks remain in “Assigned” status for more than 24 hours without user interaction. This helps catch routing issues before they accumulate.

This draft is based on general Microsoft Dynamics 365 knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

Check if your manager’s user record has the correct Worker association in the HR module. Workflow task assignment relies on the Worker hierarchy, not just security roles. If the manager’s user account isn’t properly linked to an HcmWorker record with the appropriate position hierarchy, tasks won’t route correctly even though emails are sent.

4

I’ve seen this exact issue when workflow task delegation rules conflict with direct assignment. Navigate to System Administration > Setup > Workflow > Delegation and verify no delegation rules are intercepting tasks meant for your manager. Even inactive delegations can cause routing confusion if not properly cleared. Also check if the workflow configuration has both “Assign to participant” and “Assign to hierarchy” enabled simultaneously - this creates ambiguous routing.

5

I checked the Worker associations and they look correct. The manager is properly linked to HcmWorker with the right position hierarchy. However, I found something interesting in the delegation settings - there’s an old delegation rule from last year that was supposedly deactivated but still shows in the system. Could this be causing the routing issue even if marked inactive?

7

Inactive delegation rules shouldn’t interfere, but I’d delete them entirely rather than just deactivating. More importantly, check your workflow element configuration XML. The approval step needs proper transition conditions that evaluate before task creation. If your condition logic has syntax errors or references deprecated fields, the task creates but doesn’t route properly. Export the workflow configuration and review the XML for the manager approval step - look for incomplete condition expressions or missing user assignments in the participant provider section.

8

Another thing to verify: notification configuration vs. actual task assignment are separate mechanisms. The fact that emails are being sent means the notification template is working, but the work item creation might be failing due to security context issues. When the workflow executes the approval step, it runs under the workflow system account. If that account doesn’t have permission to create work items for the target user (your manager), the assignment silently fails while notifications still go through.

Check the workflow execution log (System Administration > Inquiries > Workflow > Workflow history) and drill into the specific approval element. Look for any security-related warnings or errors that might not surface in the main workflow status.

10

I found it! The workflow execution log showed a permission error that wasn’t visible in the standard workflow status view. The workflow system account was missing the “Maintain work items” privilege for the Sales Manager role. After adding that privilege, tasks started routing correctly.