cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate III
Advocate III

State machines

Will we be able to use state machines in Flow?

 

Thanks.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Continued Contributor
Continued Contributor

Re: State machines

State machines are not available in Flow. But state machines are available in Microsoft WorkFlow Manager.

View solution in original post

6 REPLIES 6
Highlighted
Continued Contributor
Continued Contributor

Re: State machines

State machines are not available in Flow. But state machines are available in Microsoft WorkFlow Manager.

View solution in original post

Highlighted
Advocate III
Advocate III

Re: State machines

Thanks.  Do you know if there is any thought to include them in the future?  Also, will Workflow Manager and Flow be able to work together?

Highlighted
Continued Contributor
Continued Contributor

Re: State machines

Microsoft Flow is derived from Azure Logic Apps, and in Logic Apps also state machines are not available. WorkFlow Manager(WF Manager) and Flow can't work together. WF Manager is used by developers and Flow targets business users.

 

You can raise this as a feature request in Flow Ideas.

Highlighted
Advocate III
Advocate III

Re: State machines

Thank you.  I did raise it as a request.

 

If i had say a 3 step approval workflow and needed the ability to potentially send it backwards from one approver to another, is that something that could be done in Flow without a state machine?

 

 

Highlighted
Advocate II
Advocate II

Re: State machines

Right now this is the biggest limitation preventing me from leveraging MS Flow with clients.

 

Microsoft Flow currently flows in a single direction (downstream) which makes it really tough to design and implement approval-driven workflows. Without state-machines, it's really not possible to "reject to a specific step" and automate a system that accounts for the real world back and forth nature of workflows.

 

I've considered doing this with multiple flows that conditionally change-states (by starting another workflow), but it's quite cumbersome to assemble and pass meta-data between them.

 

I'd love if we had a "jump to step" action that could be called based on a condition. 

Highlighted

Re: State machines

Helpful resources

Announcements
FirstImage

Microsoft Ignite 2020

Check out the announcement of Power Platform content at Microsoft Ignite!

thirdImage

Experience what's new for Power Automate

Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Users online (4,591)