Azure BackSync workflow fails in Active Roles Sync Service due to too many scheduled triggers (4382885)

Azure BackSync workflow fails in Active Roles Sync Service due to too many scheduled triggers

An Azure BackSync workflow in Active Roles Synchronization Service may fail because it is being started more often than intended. This happens when schedules are configured in more than one place (for example, at the workflow level and also inside individual mappings). Running too frequently can overload the database and cause the sync to stop.

Symptoms

• The BackSync workflow stops or fails during execution.
• Errors mention database conflicts (for example, “deadlock” or “rollback”) or “sync steps aborted”.
• Sometimes the Sync UI shows a connection error after the failure.

 

The sync was being triggered by more than one schedule, which caused it to run too often and led to database pressure/conflicts.                                    

1) Use only one schedule

• Keep the schedule only on the Sync Workflow.
• Turn off (disable) any schedules set under Mapping items.

2) Run it less often (at least while testing)

• Temporarily set the workflow schedule to run less frequently (for example, every 3–4 hours).
• After it runs reliably, adjust the schedule as needed.

3) Save the changes and retest

• Save the changes.
• Run the workflow once manually to confirm it completes.
• Monitor a few scheduled runs to confirm the issue is resolved.