Email Notification Trigger not going out correctly

Thomas Smith5
Kilo Expert

Hello, this is my first time asking a question here so please let me know if you need any additional information.

We have a set up where when a new task is created two possible emails can be sent out:

  1. To everyone in the assignment group
  2. To the person it is assigned to

The trigger for email 1 checks to see that no one is assigned to the task, if this is the case then then email is sent out to the assignment group. 

find_real_file.png

The Trigger for email 2 checks to see if there is anything in the Assigned to field and if so sends it to that person.

find_real_file.png

The task is created in a workflow using the below advanced script:

find_real_file.png

The Problem

The problem I'm having is that the conditions for email 1 always seem to be met even if there is someone assigned to the task. 

I have done some testing and set the condition for email 1 to the below and the notification didn't go out even though the task was assigned to that person. I have also tried setting it to only run them when they are updated: this resulted in neither of them being sent out.

find_real_file.png

This has lead me to believe that there is some sort of delay between the task being created, the notification conditions being checked and the advanced script on the workflow populating the values with the correct data (which isn't triggering an update).

What I would like to do is delay these emails until all of the correct information has been added; however, I wouldn't know where to start. Any help would be greatly appreciated.

 

1 ACCEPTED SOLUTION

Thomas Smith5
Kilo Expert

Just a quick update. I had to fix this via the following work around:

  1. First I updated the workflow for this to only create tasks with an assigned to or an assignment group
  2. reconfigured the existing notifications to run only on insert.
  3. Created duplicate rules that run on update but under different trigger conditions: when the corresponding field is updated.

By doing this I was no longer getting duplicate emails going out.

This isn't an ideal fix however the team I've worked for has accepted this as a work around.

View solution in original post

3 REPLIES 3

Alikutty A
Tera Sage

Hello,

Can you change the second condition to Assigned to is not empty and test it out once?

Thanks!

Unfortunately this hasn't changed anything.

 

Thomas Smith5
Kilo Expert

Just a quick update. I had to fix this via the following work around:

  1. First I updated the workflow for this to only create tasks with an assigned to or an assignment group
  2. reconfigured the existing notifications to run only on insert.
  3. Created duplicate rules that run on update but under different trigger conditions: when the corresponding field is updated.

By doing this I was no longer getting duplicate emails going out.

This isn't an ideal fix however the team I've worked for has accepted this as a work around.