-
Title
Grouping start up configurations with Postpone and wait Concurrence Behavior results in error -
Description
In this scenario two startup configurations were created for synchronizing from target system to Identity Manager (1IM). The two startup configurations have the following setup:
1. Runs full synchronization from Target system, FULL SYNC workflow, and takes a long time to complete, e.g. 2.5 hours. Scheduled to start everyday at 8 PM.
2. Runs delta synchronization from Target system, DELTA SYNC Workflow, and takes approx. 7 minutes to complete. Scheduled to run every hour starting from 8:45 PM.
The two startup configurations are grouped together in a startup group with Concurrence behavior configured as "Postpone and wait". At the same time "Common| Jobservice | RedoDelayMinutes" was configured for 60 minutes. However, overnight job logs still show the error message for Delta Sync:
"Cannot start full sync (XXXsyncXXX) because the same full sync is still running." -
Cause
A conflict occurred when the same Delta sync workflow (e.g. Delta 2) delayed previously was blocking a new Delta Sync (e.g. Delta1) workflow. Therefore the job went to "frozen" with the error message. -
Resolution
In this case, "Common| Jobservice | RedoDelayMinutes" was set to the same time as the schedule interval for the Delta syncs.
Since, as in the example above, Delta syncs complete in 7 minutes, the configuration parameter needs to be tweaked so the restart of the Delta Sync (e.g. same syncs) and/or the schedule trigger time for new syncs will not be close to each other.
In this case changing the Delay minutes to 45 minutes solved the issue.
For information, please refer to the Target System Synchronization Reference Guide, Grouping.