Skip to main content

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

Troubleshooting an email integration

Updated on April 6, 2022

Learn about common problems that might occur in your email integration and how to troubleshoot them.

  • Troubleshooting email listeners

    Learn about common problems with email listeners and how to troubleshoot them.

  • Message processing status and error categories

    The status of an email changes multiple times as the message progresses through various processing stages. Learn about each status type to understand the email life cycle and troubleshoot potential issues with your email integration.

  • Browsing the email listener logs

    Make the investigation of issues with your email integration more comprehensive by reviewing the Log-Service-Email table.

  • Restarting an email listener

    You can restart an email listener to troubleshoot problems with the listener. For example, you might need to restart the email listener if unread messages are accumulating in your inbox.

  • Throttling during email processing

    Email providers use throttling to control the number of email messages that they receive at one time. If the number of incoming email messages surpasses a certain threshold that is determined by the email provider, the email provider might invoke throttling and drop the connection or reject additional connections.

  • Troubleshooting outgoing email

    To troubleshoot problems with sending an email from Pega Platform, review the sample scenarios and remedy steps.

  • Unit testing a Service Email rule

    Use the unit testing feature to verify that the operations of a Service Email rule function correctly before you add an external component to your testing process.

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