When using the 'TriggerFlow' action, I would expect the UI to wait for the Flow to be completed before telling the user that it's completed and display the "View updated site" button...
Observed Behavior
Right now the 'TriggerFlow' action basically does a "fire and forget" call to the Flow URL. We built an azure provisioning engine based on the following pattern in order to make sure that our logic app waits for everything to be done before completing, but it doesn't change anything since the site design does not wait for the Flow, no matter how long the Flow is running.
To me this doesn't really sens since the UI specifically shows the user that the site design as been applied, it even shows a button saying "View updated site" while we know that the site is most likely not finished provisioning...
I would expect some kind of mechanism which pokes the Flow every X seconds to see if it's completed or something like that, because as it is designed right now, it's kinda confusing for the end user.
Steps to Reproduce
Make a site design with a trigger flow action
Make sure the Flow runs for 2 minutes
Create a site based on the site design and watch the site design complete instantly even though the flow is still running
Category
Expected or Desired Behavior
When using the 'TriggerFlow' action, I would expect the UI to wait for the Flow to be completed before telling the user that it's completed and display the "View updated site" button...
Observed Behavior
Right now the 'TriggerFlow' action basically does a "fire and forget" call to the Flow URL. We built an azure provisioning engine based on the following pattern in order to make sure that our logic app waits for everything to be done before completing, but it doesn't change anything since the site design does not wait for the Flow, no matter how long the Flow is running.
To me this doesn't really sens since the UI specifically shows the user that the site design as been applied, it even shows a button saying "View updated site" while we know that the site is most likely not finished provisioning...
I would expect some kind of mechanism which pokes the Flow every X seconds to see if it's completed or something like that, because as it is designed right now, it's kinda confusing for the end user.
Steps to Reproduce