cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
wingzeroaa
Level: Powered On

Help, Flow does not triggered for Dynamics 365 Update record, in creation period

Hi,

 

I have a strange scenario here for Dynamics 365 and Flow.

I create a Flow, which is triggered when a record in Dynamics 365 is updated.

 

It will be triggered, if I manually update the record later.

However, when the record is created, it is updated several times backend, by Dynamics 365 workflow or JavaScript, but no flow is triggered.

 

I can see in the Audit History, just after record is created, it is updated several times in short period.

No Flow is triggered.

 

Later, come back to record form, run any workflow or manually update any field for the record.

The Flow will be triggered.

 

 

Are there any conditions, such as only trigger Flow, after 1 mimute of creation, if the trigger is Update?

Hope my explaination is clear.

Thanks a lot for any help.

 

Regards,

Zhenyu

4 REPLIES 4
wingzeroaa
Level: Powered On

Re: Help, Flow does not triggered for Dynamics 365 Update record, in creation period

CreateUpdateSeveralTimes.pngManuallyUpdateLater.pngOnlyTriggeredOnce.png

 

Picture 1: Create and Update several Times, Flow does not triggered

Picture 2: Come to Dynamics 365 record and manually update record

Picture 3: Flow is ONLY triggered by manually update in Picture 2

RyanMesser
Level: Powered On

Re: Help, Flow does not triggered for Dynamics 365 Update record, in creation period

I also have this issue, any workaround?

Highlighted
wingzeroaa
Level: Powered On

Re: Help, Flow does not triggered for Dynamics 365 Update record, in creation period

Hi RyanMesser,

 

For now, I just put 2 minutes wait condition in the workflow, then trigger the update.

It works.

 

In future, I am thinking, create a middle entity record, save all informatin needed.

Then trigger the Flow on the creation of that middle entity record.

RyanMesser
Level: Powered On

Re: Help, Flow does not triggered for Dynamics 365 Update record, in creation period

Unfouratnetly the workflow is a real time workflow which I don't think you can put wait conditions in?

I'm starting a child workflow from within the processs that runs first of when a case is created that makes Flow think its been updated but its a bit of a strange limiation in my opinion.


@wingzeroaa wrote:

Hi RyanMesser,

 

For now, I just put 2 minutes wait condition in the workflow, then trigger the update.

It works.

 

In future, I am thinking, create a middle entity record, save all informatin needed.

Then trigger the Flow on the creation of that middle entity record.


 

Helpful resources

Announcements
firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

firstImage

Incoming: New and improved badges!

We've given our badges an overhaul and also added some brand new ones!

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

sixthImage

Power Platform World Tour

Find out where you can attend!

seventhimage

Webinars & Video Gallery

Watch & learn from the Power Automate Community Video Gallery!

Top Solution Authors
Top Kudoed Authors (Last 30 Days)
Users online (6,138)