Dynamics 365 When a record is created or updated runs against old records

[LauraWare]

I have a flow that uses the new Preview trigger from Dynamics when a record is created or updated.  When I turn on the flow, it runs thousands of times against our Dynamics 365 Tasks entity.  Is there a known bug with this trigger?

In the data, I can see these rows are from old created or modified data rows.  See the data here.

Subject
XXXXXXXXXXXXXXXXX

Task Record Type Label‌

Activity Status
1

Activity Status Label
Completed

Actual End
2017-03-16

Category
Activity

Created By
6fa58d16-9ac8-e611-8103-5065f38a2981

Created By Type
systemusers

Created On
2017-03-16T18:27:48Z

Due Date
2017-03-16T18:07:50Z

Is Billed
false

 
Modified By
xxxxxxxxxxxx

Modified By Type
systemusers

Modified On
2017-03-16T18:27:55Z

New Activity Label‌

New Meeting Type Label‌

New Priority
1

New Priority Label
Normal

Owner
xxxxxxxxxxxx

Owner Type
systemusers

Percent Complete
100

Priority

1

Priority Label
Normal

Regarding
xxxxxxxxxxxxx‌

Regarding Type
contacts

Start Date
2017-03-16T18:07:50Z

Status Reason
5

Status Reason Label
Completed

Task
b47d2141-760a-e711-80fa-5065f38a3b81

Time Zone Rule Version Number
0

[v-xida-msft]

Hi @LauraWare,

Could you please share a screenshot of your flow’s configuration?

Do you add a “Update a record” action within your flow?

Further, does your flow run thousands of times when a record is created in your Dynamics 365 Tasks entity?

I have made a test on my side and don’t have the issue that you mentioned. My flow’s configuration as below:

The flow works successfully as below:

 

If you add a “Update a record” action within your flow, you should consider avoid being trapped in an infinite loop within your flow.

In addition, please check if there are some records created or updated in your Dynamics 365 Tasks entity when your flow is turned off.

Best regards,

Kris

[LauraWare]

Hi There,

I do have an update task in my flow - but my flow checks to see if there is an email event id, if there isn't one, I add one then the flow is triggered again (because it is updated).   So the flow will run again on update, however, it meets that criteria and stops when it has the eventid.  So each flow runs 2 times (created and updated). 

That is not my issue, however.  I don't understand why the trigger is triggering against records that were created or modified in 2017.  Those were not Updated or Modified within the last 5 minutes of the run.  

 

[LauraWare]

Just to follow up, it does not run against the same record thousands of times, it runs through all of my old records.