Power Automate flow running forever

(0) Share

Report

Posted on by AlanCruz

Hey guys,

I'm facing a problem with a specific automation.

My flow starts, but at some random point, it doesn't go to the next step and the flow keeps running forever and doesn't end.

Does anyone know what this could be?

Categories:

Using flows

I have the same question (0)

All responses (7)

Answers (0)

Sort by

creativeopinion 10,508 Moderator on at

Like (1)

Report
Copy link

Link copied!

@AlanCruz Do you have a Get response details action in your flow? Can you try to add that after your flow trigger?

Also, can you expand your actions and upload a screenshot of your flow? It'll be easier to troubleshoot when I can see your entire flow.

For more flow troubleshooting tips—check out this YT Tutorial: 5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows
In this tutorial I cover:
✅ How to troubleshoot a false Condition action result
✅ How to get dynamic content when it isn’t selectable from the list of dynamic content
✅ How to troubleshoot an Apply to Each action that isn’t looping through
✅ How to troubleshoot a skipped Apply to Each action
✅ How to troubleshoot a Filter Query
✅ How to use a SharePoint yes/no column in a Filter Query
✅ How to use Compose actions to troubleshoot a Power Automate flow
✅ How to troubleshoot multiple emails being sent
✅ How to troubleshoot multiple Teams messages being sent

Was this reply helpful? Yes No
AlanCruz 12 on at

Like (0)

Report
Copy link

Link copied!

@creativeopinion

I sent 2 prints, the 1st of the flow in more detail and the second of another execution that was running forever.
As you can see, the flow simply gets stuck.
The action ends but does not proceed to the next action, and in this way the flow keeps running and does not finish.
I set a delay so that after 10 minutes the flow would be closed, but according to the 2nd print the action is finished but the next one is not called.

Was this reply helpful? Yes No
creativeopinion 10,508 Moderator on at

Like (0)

Report
Copy link

Link copied!

@AlanCruz Is there a reason that you have nested the Get response details in the Do until action? Once a form has been submitted, the response details should be available immediately... are you experiencing some sort of delay after a response has been submitted?...

Was this reply helpful? Yes No
AlanCruz 12 on at

Like (0)

Report
Copy link

Link copied!

@creativeopinion Not a delay, but an error.
This nesting is due to me receiving a message stating "Warm data is locked", and because of this it was not possible to obtain the response details.
So I did this Do until loop to check the statusCode of the Get response details action, and if it is 400 it will try again up to the limit of 60 loops, which is the default for this connector.
I believe this happens because this form is filled out several times per minute.

Was this reply helpful? Yes No
creativeopinion 10,508 Moderator on at

Like (0)

Report
Copy link

Link copied!

@AlanCruzI think the delay shouldn't be in a parallel branch. It should be above (or below—doesn't really matter) the Initialize Variable action.

Also, to evaluate your condition, you should insert a Compose action above the Condition with the expression to output the Status Code (this will help to troubleshoot the flow).

Was this reply helpful? Yes No
AlanCruz 12 on at

Like (0)

Report
Copy link

Link copied!

@creativeopinion I applied your solution and also tried other alternative solutions, but I still have the same problem. Randomly my flow stops and the next step is not executed.
Could I be reaching a flow limit? Because it doesn't make sense for the flow to stop and not display any error messages.

Was this reply helpful? Yes No
creativeopinion 10,508 Moderator on at

Like (0)

Report
Copy link

Link copied!

@AlanCruz According to this Microsoft article, you're limited to 300 API calls per connection within 60 seconds and one trigger poll every 86,400 seconds. Keep in mind this article was from Dec 2022... not sure if this still the case.

Was this reply helpful? Yes No