Flow Step (Preview) fails to trigger the Flow from a BPF in a Dynamics Model Driven App

[aussiejedi]

I am seeing some inconsistent behaviour when attempting to kick off a Flow from a Business Process Flow in a Model Driven App.

I have a built a very simple Solution which consists of:

- A custom CDS entity

- A Business Process Flow which includes a Flow Step (Preview) action which is configured to trigger a Flow

- A Flow (the one configured to be triggered by Business Process Flow) which has a single trigger (When a record is selected (from my custom CDS entity) and a single action (a Compose - just for simplicity in testing))

- A Model-Driven App which includes the custom entity and the business process flow

When I run the model-driven app using the new Edge Dev (Chromium), the Run Flow button works as expected and allows me to run the Flow.

After selecting Run flow from within the BPF, the overlay window appears as below, allowing me to successfully kick off the Flow. Note that the title of the overlay window is 'Login Successful'.

However, if I use any other browser (Chrome, IE11, Edge (not Chromium)), when I select Run Flow from the BPF, I briefly see an overlay window appear, but it is blank (other than the title 'Login to flow'). This overlay window then disappears.

After the overlay window disappears, the BPF reports that the Flow is 'Processing', however, the Flow has not started and does not appear in the Flow History.

I asked a colleague to test the behaviour and they have experienced the exact same behaviour as me (the Flow triggers correctly from Edge (Chromium) [in their case Canary], but not in any other browser. Interestingly, I have another machine where even in Edge Dev (Chromium) the Flow will not trigger and the overlay window simply disappears.

I have tried running Fiddler traces and (Dev Tools) Network traces but have not seen any failed calls or errors that indicate the underlying issue.

Has anyone else experienced this and/or have any suggestions as to what might be going on?

Thanks!

David

[v-litu-msft]

Hi @aussiejedi,

Sorry, I never met this issue, there is a document about Instant flows in business process flows, hope it can help you something:

https://docs.microsoft.com/en-us/business-applications-release-notes/april19/microsoft-flow/instant-...

This feature is still in preview so it would be some shortcomings and faults, you could wait for a while, and then use it after this function is more perfect. We will pay attention to your feedback, and if this is a widespread issue, we will report it.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[SamWallis]

Hey @v-litu-msft,

I'm also experiencing this bug across multiple browsers. 

This will become urgent soon as we prepare for product deployments.

An acknowledgement of the issue and ETA / at least commitment to fix from the Dynamics team would be much appreciated.

Cheers,

Sam

[SimonSays]

Same issue here. Worrying there's no acknowledgment of this issue nearly 4 months on.

[mayankchaudhary]

I am facing the same issue. Any fix or solution will be really helpful!

[SimonSays]

@mayankchaudhary I seem to have found a way to get the flow dialog to function. If I click Flow in the header menu and wait a few seconds, the Flow that I created is listed in the drop-down menu and I can execute it from here. This seems to consistently work for me.

[mayankchaudhary]

Thanks for the way around! But this trick only works in Edge browser and not chrome. Are you facing the same issue as well?

[SimonSays]

@mayankchaudhary This appears to work in Chrome too. Be patient when you click the flow drop down in the menu though. I found it takes a few seconds to load the list of flows associated with the BPF. Once the drop down is loaded the flow buttons in your stages work too.

[Anonymous]

I am still looking for a solution to this as well. I am new to the Model Driven Apps and I am experiencing this still.

[donalmc]

Has anyone solved this?

I tried switching to the new CDS Current Environment When a flow step is executed trigger, and this behaves in the same way, as on it adds a Run Flow button to the stage; however, the Flow menu trick does nothing at all here (which isn't something you could go live with anyway) and you get stuck at the 'Login to flow' screen.

[Anonymous]

It still happens to me. I ended up removing the one input that a person could do (it was just adding personalized text to an email) and ended up just adding that flow into my BPF so when it changed stages it triggered instead. No idea if that is a useful thought for you, all depends on what the flow is.

[donalmc]

I changed to a workflow that triggers when you exit the stage - not great as the user has no interaction, but at least it moves on.

[Anonymous]

I have the same issue. 

Still no one has a solution for this?

[Django]

Same here: very simple Flow in very simple Business Process Flow:

Would be very cool integration though 👍

[Anonymous]

so.. just checking if this has been resolved? 

[Anonymous]

As far as I know, it has not. I have not had time to test it super recently though.

[Takehiko05]

I had the same problem with Edge and solved it with the following method.
・Clear the cache and cookies.
・Restart Edge.
it takes about 10 seconds to appear "Run Flow" screen

Postscript
I'm not sure, but If you use the Edge profile with the same account as Power apps, the problem may recur. I avoided using the Edge profile and so far it has worked fine.

[Treebys]

I had a similar issue today with a first time user. Tried refreshing the browser multiple times, opening and closing it etc then I realised what it was struggling with was Power Automate so just got the use to open Power Automate in another tab and then close it back down. This seems to have 'triggered' their account and they could then run the flow.