Skip to main content

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.

Support Article

Email sent out twice

SA-9495

Summary



Flow contains CorrNew utility used to send an email to a WorkParty Role and also CC-ing it to another Party.
After the email is sent out, the recipients get a duplicate copy of the email every time.



Error Messages



03:53:15,819 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 1_circum0
03:53:15,819 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 2_circum0
03:53:15,819 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 3_circum0
03:53:15,819 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 5_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 6_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 7_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 8_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 9_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 10_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 11_circum0
03:53:15,820 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 12_circum0
03:53:15,832 [ PegaRULES-Batch-4] (pages.DeclarativePageUtilsImpl) WARN - Required parameter'pyUserIdentifier' for data page 'D_Employee' cannot be blank.
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 14_circum0
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 15_circum0
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 16_circum0
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 17_circum0
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) ERROR - Data-Corr-Email that failed to send has pzInsKey of : DATA-CORR-EMAIL PegaSample EM-2922!20150429T075304.382 GMT
03:53:17,703 [ PegaRULES-Batch-4] ( Send.Data_Corr_Email.Action) DEBUG - Running step 18_circum0
03:53:17,703 [ PegaRULES-Batch-4] ( OnSend.Data_Corr_.Action) DEBUG - Running step 1_circum0
03:53:17,706 [ PegaRULES-Batch-4] ( OnSend.Data_Corr_.Action) DEBUG - Setting pyRecoverableError to: 0

.
.
.

Steps to Reproduce



Load a Data Page without passing mandatory parameter during Email processing.


Root Cause



The root cause of this problem is a defect in custom application code/rules. There was a requestor level Data Page which had a mandatory parameter. But when the SendCorr agent requestor was initialised, this parameter was not passed through which generated an error. Even though this error would not stop the sending of email, the error triggered re-queuing of the email as Pega would think something stopped from email to process successfully.

To prevent re-queuing you need to remove the error. Change the Data page parameter to not mandatory.


Resolution



This issue is resolved through the following local-change:

Change the Requestor Data Page to have a non-mandatory parameter. This removes the error it would throw during Correspondence processing, leading to re-queuing of the emails.
Suggest Edit

Published September 18, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us