Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Exception handling

Updated on September 13, 2021

Pega Smart Dispute for Issuers uses the MCOMClaimsMgrConnectionProblem flow to handle any connection errors that might occur when services are invoked.

In the case of an exception, the MCOMClaimsMgrConnectionProblem flow is invoked from the InvokeMCOMClaimsMgrService flow. Then, the assignment is routed to the Exceptions work queue. Open the assignment to view the details about the interaction with the failed service and retry the service or resolve the case.

Note: You can attempt retrying the service only after you resolve the errors in the data that caused the exception.


To customize exception handling, override the MCOMClaimsMgrConnectionProblem flow. In addition, to extend exception handling by overriding or adding processing steps, override the MCOMClaimsMgrErrorHandlingTemplateExtension data transform.


Smart Dispute for Issuers 7.4 - 7.41 Smart Dispute for Issuers Low-Code App Development Financial Services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us