Email Template not getting picked up

[VivekTangri]

We have an email template already configured in connection which is used whenever a job fails.
However, we have received one instance where the email template has not been picked up. Rather a autogenerated email was triggered to an inactive user with disabled email account.

Can someone help us understand where can the email address being getting picked from ?

[rushikeshvartak]

Can you provide more context?

• what kind of job is running - connection means import job?
• user email ??

[VivekTangri]

@rushikeshvartak 

• what kind of job is running - Accounts Import Job
• connection means import job - Connection has an option of selecting email template. Thats the one which should have been picked but isnt
• user email - email of an user

[rushikeshvartak]

• Connector level email template trigger when import job failed.
• if its not working then its issue with dynamic variables used in email template body. 
• Please confirm connector type.

[Raghu]

@VivekTangri  failed job Connector level template mapped ? if yes check template cc/to?

[VivekTangri]

@Raghu 

Unfortunately, the Connector level template (which has been configured and working) was not picked up.

[VivekTangri]

We had raised a ticket for the same where the Saviynt team analyzed and provide us the below response.

The root cause of your problem has been identified. Kindly refer to the analysis provided below for further details.

Issue:  An email notification of job failure was triggered using an unconfigured email template and an inactive user's email ID.

Cause: As part of improved job management, Saviynt blocks the concurrent execution of conflicting jobs. In the event of failure while executing conflicting jobs, the RESPONSE column in the Job History Details page displays the Reason for failure. EIC also sends an email notification to the user that triggered the job or to the user who created the trigger notifying the user that the job is being blocked from execution due to a concurrent job that is already being executed.

Remediation: This is the expected product behavior. To prevent this issue from occurring again, you may recreate the job trigger.


Please refer to the article below for more information.
https://docs.saviyntcloud.com/bundle/Release-Notes/page/Content/v23/Release-Notes-23-1.htm#Improved

[rushikeshvartak]

This should be bug/ enhancement . if client changes vendor then all users who created jobs in past and we are asking to create all jobs again . This should be fixed as defect.

I have created idea for same. https://ideas.saviynt.com/ideas/EIC-I-5873 

[VivekTangri]

True. This is something we are not accepting as a remediation.
hope they fix it it coming release

[rushikeshvartak]

Upvote idea

[VivekTangri]

Guys,
Had a call with Saviynt and they mentioned that this is an enhancement that they have had in recent release.
https://docs.saviyntcloud.com/bundle/Release-Notes/page/Content/v23/Release-Notes-23-1.htm#Improved

Improved Job Management

Saviynt now blocks the concurrent execution of conflicting jobs. In the event of failure while executing conflicting jobs, the RESPONSE column in the Job History Details page displays the Reason for failure. EIC also sends an email notification to the user that triggered the job. By default, the concurrent execution of different categories of user import jobs is restricted through the new Block Concurrent execution of UserImport jobs setting in Global Configurations. For more information, see Managing Jobs in the Enterprise Identity Cloud Administration Guide

Have created an idea to let admins provide an email rather than picking up the default by itself.
Can you please upvote it ?
https://ideas.saviynt.com/ideas/EIC-I-5882 

[rushikeshvartak]

Same idea was already raised 🙂