Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
01/29/2024 11:16 AM
We have run multiple certification campaigns in our production environment, and on each we have experienced a failure of the fourth notification email reminder. Every other aspect of the certification is working correctly, and every other email notification is sent successfully to the intended recipients in the proper format.
We have checked the Certifications table and confirmed that the REMINDERMAILSENT, SECONDREMINDERMAILSENT, THIRDREMINDERMAILSENT, and FIFTHREMINDERMAILSENT are all = 1. Only this one, FOURTHREMINDERMAILSENT, is null.
We have tweaked the bind variables in the email template but are still getting a failure. The error message in the logs for the CampaignReminderJob on the day this notification was to go out is "ERROR campaigns.CampaignService - Fourth notification email fails with params campaign-com.saviynt.ecm.campaign.domain.Campaign : 37 user-023788 and certification-com.saviynt.ecm.campaign.domain.Certification : 61" Again, all other notification emails were sent as intended, including the one after this one. This is the fourth in a series of five.
01/29/2024 11:21 AM
Are you using any different binding variable for 4th reminder email which is resulting in failure?
01/29/2024 11:30 AM
01/29/2024 12:16 PM
Does it working without binding variables ?
01/29/2024 01:33 PM
We are pretty sure we figured it out. We found an invalid bind variable in the body of the email.
01/29/2024 01:50 PM
To get what variables are present to use in the email template, check using the below expression. By putting it in the email body, it will print all variable names with values, and then accordingly, you can use it:
${this.binding.variables.each {k,v -> println "$k = $v" + "" + "br" + ">"}}
you can check which variables used.