Synchronous Flow inside Model App

[BenDenBlanken]

Hi All,

I am looking to fill a requirement with Flow which we would previously use synchronous workflow.

I was wondering if synchronous flows from inside a model-app will ever be possible? We were promised that Flow is ultimately going to reach parity with workflow functionality.

However when reading the following passage from the documentation I am starting to wonder if we will ever see synchronous flows inside model apps:

• What about synchronous workflows?

  You should re-evaluate the need for synchronous workflows to identify whether the objective, or parts of the workflow can be built using a flow. In particular, we see from our telemetry that synchronous workflows are a significant contributor to overall end user poor performance experience. For many uses though it would be preferable to split these actions out as asynchronous so that the user can continue with their activity while Power Automate continues to ensure completion of the action.

Can you give me a definitive answer on the matter?

[v-alzhan-msft]

Hi @BenDenBlanken ,

Could you please share more details about your requirement?

Best regards,

Alice       

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

[BenDenBlanken]

Hi Alice,

Thanks for responding. We have a few usecases where synchronous flows would be very handy. All usecases are UX cases mostly like:

1. Set the name of the entity OnCreate. Our best practice is to generate a 'name' field for some entities. You want to see what Name the entity has gotten after the create without manually having to refresh the model.
2. We generate an email template on demand. We want the user to edit the email before we send it from the modelapp. When we use the "execute flow" button the email template gets generated in the background. However the user never gets a notification it has been created and needs to refresh the app a couple of times before she sees the template has been created. In this case our customer sais this is unacceptable.

Ofcourse there are workarounds to these issues. But synchronous flows and thus flow-workflow parity would resolve this.