Manage failed connector shipments

When an artifact fails to ship, it is stored in the Failed Connector Shipments table. You can examine it, correct the problem, and replay it. Or you can fix the problem and re-run the connector. When the artifact ships successfully, you can mark older versions as fixed.

• In the CollabNet Sites view, right-click a repository mapping or specific mapping direction and select Show Failed Shipments.

  Here's an example:

  
• To narrow down your list of artifacts, click the Filters icon. You can choose from a variety of filters such as exception details and participating system attributes.
• To add or remove table columns, click the View Menu icon and then Columns. In the Preferences window, select the columns you want displayed.
• To view the XML representation of an artifact that failed to ship, right-click that row in the table and select Examine quarantined artifact.
• To see the exception that caused the artifact to fail, the stack trace and other details, right-click an artifact, select View Details and click Exception Details.
• For details on participating system attributes related to the failed shipment, right-click the artifact, select View Details and click Failed Shipment Details.
• Let's say an artifact failed to ship, you examined it and corrected the reason for failure. To now replay it, right-click the artifact and select Replay.
  Tip: You may want to filter the artifacts based on specific criteria and replay a bunch of them.
• Let's say an artifact failed to ship due to an incorrect mapping. You subsequently updated the mapping and re-ran the connector so that synchronization succeeded and the artifact was shipped. However, the Failed Shipments entry for the artifact could still exist. To denote that this is now fixed, select the artifact in the table and click Mark as fixed.