Resolving blocked synchronization

Synchronization of an object can be blocked if a dependent object cannot be synchronized. To resolve the blocking problem you need to fix the underlying problem with the dependent object.

About this task

A common cause of blocked outgoing synchronization is the absence of a required user record in ClearQuest®. For example, if you create a work item and assign it to a user, outgoing synchronization fails if that Jazz™ user does not map to a ClearQuest user. To resolve the problem you must use the ClearQuest User Administration Tool to create a user record whose Login, Name, and E-mail field values match the User ID, Name, and Email address field values, respectively in the Jazz repository.


To resolve a blocked synchronization operation:

  1. Open the Team Dashboard view and scroll down to the Event Log or Events section. Look for an entry that states, "Synchronization is blocked (WorkItem number/synchronization_rule_name." Click the entry to see more information, such as "Synchronization has been blocked until other required items have been initialized."
  2. Double-click the entry to open the Synchronization Status page for the event. Click the link in the Blocked by field to open the Synchronization Status page for the event that is causing the problem.
  3. The Synchronization rule field contains a link to the synchronization rule that the operation was unable to carry out. For example, the sample rule defines which fields of a ClearQuest user record must map to which properties of a Jazz user item. The Current State section shows the values for the item properties and corresponding ClearQuest record fields involved in the synchronization operation. For example, an outgoing synchronization error caused by the absence of a corresponding user record in ClearQuest would show the UserID, Name, and Email Address property values with no entries for the corresponding ClearQuest fields.
  4. After you fix the problem causing the blocking error, click Retry Incoming Synchronization or Retry Outgoing Synchronization. You can select multiple items and retry synchronization of them. By default, the synchronization operations of up to five items that you select are performed in parallel. If you select more than five items to retry, the first five are processed in parallel, then the next batch of five or fewer items are processed in parallel, and so on until synchronization operations for all selected items are done.
    Note: To change the number of items that can be processed in parallel, add the following property to the install-directory\eclipse.ini file: – where n is the number of items. If you specify a large number of items to be synchronized in parallel, performance can suffer.


If no other problems exist, the synchronization operation succeeds and the Synchronization status changes to OK.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki