Flow Sending Duplicate emails for Leads

[AndresSilvera]

Hi There, I have a reoccuring flow which runs every 2 weeks and is supposed to list all records from the LEads table in Dynamics sales professional, Then there is a condition to check and ensure that the status is still open, and that the LEad follow up date field if Is either Null or less than todays date, and if so, trigger an email to the Record owner with details of the Lead and specific instructions.

The problem Im having is that the flow is sending out duplicate emails over and over and I cant seem to figure out why.

Below is a snippet of my flow steps

[trice602]

Hi @AndresSilvera ,

On the surface I would change the condition to the following:

AND

Status equals Open

Date less than or equal to formatDateTime(utcNow(),'yyyy-MM-dd')

From here, see what the results look like, and you can bake in the null values but what I like to do is get the results for the main condition first then look at null values next.

[AndresSilvera]

Thank you, but do you mean add the Null value logic to the same condition box, or add another condition box for it later.

With the current setup, it is pulling in the correct amount of Open Leads which meet my the condition criteria, its just that its sending duplicate emails over and over in a continuous loop for some reason which I cannot figure out why

[trice602]

Hi @AndresSilvera ,

There are two root causes to work through:

1) is the condition, is it working by design?  Your response is yes so there's no need to modify the condition.  I was under the impression it was grabbing incorrect rows because the send email is going to send emails based on the condition.

2)  What duplicate email is it sending?  Can you share your expanded send email action please?  My thought process here is that null values are creating that duplicate emails in each recurrence.  If it is sending a duplicate email from the previous run the follow-up date value is null, or less than today's date, or still Open.

Please share a specific example such as:

"...this email is a duplicate and here are the condition's values..."

Follow-up date:  2023-xx-xxxx (or null)

Status: Open

[AndresSilvera]

Here is the send email section expanded, I do have a step before this which checks the Owner ID of the record, then the User table in order to obtain the owner Ids email address to send them the reminder

This is an example of a duplicate email, the same email was triggered multiple times and the information on the email itself is exactly the same on each email received.

[trice602]

Hi @AndresSilvera ,

Thanks for sharing, helpful.  So to clarify, the duplicate emails are in the same run?

[AndresSilvera]

Thats correct, the duplicate emails are being sent out on the same run

[trice602]

Hi @AndresSilvera ,

Thanks, understood.  Ok, when looking at the flow again, I think the issue is grabbing the email address action.  I don't see a specific Dataverse action named 'Get User Email by ID'.  What is this action by default name?

Because what I think is happening is you are listing rows that meet the condition which is confirmed correct.  But then you are grabbing rows again in the loop to get the email by ID; it's this 2nd action that is creating duplicate emails.

Can you use 'Get user profile (V2)' instead?

I'm confident we close to solving this. 😀

[AndresSilvera]

Thank you for the help, I was able to make the change you suggested, but now im receiving the below error message which I never used to receive before

InvalidTemplate

Unable to process template language expressions for action 'Condition' at line '0' and column '0': 'The template language function 'less' expects two parameter of matching types. The function was invoked with values of type 'Null' and 'String' that do not match.'.

[trice602]

Hi @AndresSilvera ,

This means one of the dates are blank.  Try moving the 2nd condition to the top position and re-submit the previous please.

[AndresSilvera]

Thank you, that allowed the test to run, however now the flow has been running for over 43 minutes and has still not concluded or triggered any emails. this seems excessively long as in total there are only 277 records to run through