We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Single campaign email reminder failing

leed02
New Contributor
New Contributor

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.

5 REPLIES 5

dgandhi
All-Star
All-Star

Are you using any different binding variable for 4th reminder email which is resulting in failure?

 

Thanks,
Devang Gandhi
If this reply answered your question, please Accept As Solution and give Kudos to help others who may have a similar problem.

leed02
New Contributor
New Contributor
Name : Campaign Escalation Email 1
To : ${usersManager?.email}
Cc :
Subject : Escalation Action Required: Certification is DUE
 
Name : Campaign Escalation Email 2
To : ${users.email}
Cc : ${campaign?.campaignOwner?.email},${usersManager?.email}
Subject : Escalation Action Required: ${campaign?.campaignName} is PAST DUE
 

Does it working without binding variables ?


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

We are pretty sure we figured it out. We found an invalid bind variable in the body of the email.

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.


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.