Handling solution processing errors

Provides troubleshooting tips that can be used to diagnose error conditions, identify where in the process flow errors might have occurred, and recover from error conditions.

Description

The Product Information Management for Retailers solution is designed so that its component collaboration objects gather as much information as possible about an error situation, notify the appropriate users that an error has occurred, and then continue with item processing. Only severe system errors cause processing by a collaboration object to end as an unfinished flow. This design prevents situations in which a restarted flow might not have all of the resources available to it to reprocess the item or might initiate tasks that should not be repeated. The following examples describe some of the problems that can occur if item processing is restarted:

  • If an item is approved in the business process but the synchronization fails on the back end, if the process is restarted, the item will not be found in the item store (it has already been deleted).
  • If an item is synchronized to the back end but an error occurs when sending the response to UCCnet, if the process is restarted, the item will be synchronized to the back end again.
The following lists several error situations that can occur when processing an item:
  • A UCCnetMessageReceive collaboration object cannot parse the incoming message into a specific item request.
  • A database access failure occurs during processing by ItemValidation, ItemCollector, ItemDispatcher, or Process_Reviewed_Item collaboration objects.
  • The business review/approval process ends in error.
  • An item cannot be synchronized to the back-end system.
  • A response cannot be sent back to UCCnet.

Parent topic: Solution Development Guide