Enable resetting of aborted startup sequences for synchronizations (4331197)

When a DPRStartSequence is started, a new entry is created in DPRStartSequence with ExecutionState="Running".  As soon as all contained syncs are processed, the ExecutionState changes to "Processed".  This also happens if a sync involved fails.  However, if a sync is not terminated regularly, e.g. due to a job server crash, the ExecutionState remains at "Running".

If IsAllowMultipleInstances is not set, all subsequently started sequences will fail with:

"[1779024] Cannot create an instance of the start up sequence (AD+Exchange) because there is already an active instance. Multiple instances are not allowed for this start up sequence."

There is no regular way to reset (or delete) the canceled sequence.  A correction must currently be done via SQL (or Object Browser).

The StartSequence editor in the Synchronization Editor should provide this possibility.

This is found in Synchronization Editor | Database | Manage Start Sequences... | Show Instances. Then the instance can de selected and deleted.

Additionally, it would be useful to display the runtime of the started instances as well.

An enhancement request (#33050) has been created.

WORKAROUND

Reset via SQL or Object Browser.

STATUS

The product team will evaluate the request and this feature may become available in a future release of the product.