Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Error handling in connectors

Error handling in connectors

Connectors are used to write data to or read data from an external system. Since connectors communicate with external systems, the possibility of something going wrong always exists. Therefore, a best practice is to include error handling for all connectors. The following table presents both types of errors that can occur when integrating with an external system, as well as best practice strategies for each.

Error type Description Example Action strategy
Transient Errors These errors are temporary and usually correct themselves over time.

The connector is unable to connect because the application is being restarted and is temporarily unavailable.

Post a note to alert the end user that the integration failed and ask the user to retry at a later time. Alternatively, if the response is not immediately needed, the connection can be automatically retried.
Permanent Errors These errors are typically due to a configuration error or an error in the remote application logic. An invalid SOAP request is sent to a SOAP service. The error persists until the SOAP request message is fixed. Write the details to a log file so that errors can be investigated and fixed. In addition, you might want to implement a process for the investigation and fixing.
Integration Error 0

Check your knowledge with the following interaction.

This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice