# Resolving Distribution Errors

Data distribution errors and pending updates are collected and displayed in the MiCollab Distribution Error application. If there are errors, a warning message is displayed at the top of the server manager interface. The message is a reminder to resolve the errors. It goes away when there are no more errors or when the check box to skip the message is selected. You must resolve data distribution errors that were initiated from MiCollab USP from the Distribution Error application. To resolve distribution errors:

- review the updates

- retry the updates

- correct the data conflict and then delete the update, or simply delete the update if you determine that the update is not required

## Review Updates

1. Under Administration, click SDS Distribution Errors. The pending updates and errors are listed.

2. Click Reload to refresh the table. If new distribution errors occur while you are viewing the table, the table is not updated automatically. You must click Reload to see the latest view.

3. To customize the way data records are displayed, you can right-click on the column header and

   - Sort Ascending: sort the column data in ascending order.

   - Sort Decending: sort the column data in descending order.

   - Group by Form Name: allows you to group records by form name

   - Ungroup: click to ungroup a previously grouped set of records.

4. Click the icon to display the details for a specific record.

## Retry Updates

To manually retry updates:

1. Select a record that has a Status of "Idle". Only "Idle" records can be retried.

2. Click Retry, select Retry Selected, and then click OK to update the remote node with the record from the local node. "Retry Pending" appears in the Status field of the record. If the update is successful the update record disappears from the list. If you retry an update and the update fails, the record is temporarily highlighted.

   Note: To retry all idle records, click Retry and then select Retry All, and then click OK. If you have applied a filter to the list, then Retry All only applies to the displayed "Idle" records.

3. Click Reload to update the main window with the latest data.

   Note: The system automatically retries "transport" errors. Updates that are fixed by the system will disappear from the Distribution Errors window after a Reload.

   The system automatically retries data updates that are not successfully transported to the destination element (due to a network or element failure). The following conditions apply to system initiated automatic retries:

   - Automatic retries are started every 30 seconds.

   - Updates are retried from oldest to newest based on the initial time stamps of the record.

   - Automatic retries yield to manual retries and new updates.

   The following data updates are not automatically retried

   - updates that fail because an application on the destination element was unable to write the data to its database

   - updates that fail because the same data was updated concurrently.

## Delete Updates

1. Correct the data conflict on the network element or confirm that the update is not required.

   Note: Deleting an error record could result in data inconsistencies that cause subsequent retry operations to fail because of a dependency between the records. Only delete an error record if you understand the error and have determined that the update is not required.

2. Select a record that has a Status of "Idle". Only "Idle" records can be deleted.

3. ClickDelete, selectDeleted Selected, and then clickOKto remove the record. If the delete operation fails to remove the record, the record is temporarily highlighted.

   Note: To remove all idle records or all selected idle records, select the Delete All or Delete Selected options and then click OK. If you have applied a filter to the list, then Delete All only applies to the displayed "Idle" records.

4. Click Reload to update the main window with the latest data.