Power Automate "Do Until" action does not obey loop conditions.

Question

I have a flow that requires sending paginated HTTP GET requests to Notion. a Condition action triggers a nested Do Until action if the returned 'has_more' value from the first request is $true. The returned 'next_cursor' value is set to a variable, which is then piped into a subsequent request's query string. This is supposed to run until either the 'has_more' value returns $false or the 'next_cursor' value is $null.

However, I've had no success getting the Do Until action to proceed further than the first run. Depending on the conditional rule, the action A) succeeds after only one iteration, or B) runs for 16 minutes and fails with the error "An action failed. No dependent actions succeeded." No further details are provided, and each action in the loop runs exactly as intended with no skips, fails, or timeouts. I migrated the action to sequential Condition actions with the exact parameters I set for the loop. This works exactly as intended but isn't ideal; eventually someone will have to manually paste another conditional action and increase the complexity of the flow.

Steps I've taken to remediate this:

• Expanded the timeout values for the Do Until action
• Manually set boolean variable to compare against 'has_more' variable rather than typed in the conditional
• Initialized an integer variable and included an Increment Variable action within the loop to stop the Do Until action after (x) loops
• Moved the Do Until action out of the Conditional action
• Added a Delay action to rule out potential unreported request limit errors

fig. 1: Do Until action run example.

fig 2: Current workaround.

Answer 1

Dear Customer, To resolve this, Microsoft’s support team will need to step in. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis.As forum moderators, we don’t have access to the detailed logs or backend systems needed to troubleshoot this effectively due to privacy and security constraints. For that reason, the most efficient solution would be to contact Microsoft’s support team directly.For the standard procedure outlined above, Office 365 global administrators may need to contact the Office 365 support team by submitting a service request.Here’s what your Office 365 Global Admin should do next:

1. Submit a Service Request: The Global Admin should create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.
2. Find Your Microsoft 365 Admin: If you’re unsure who the Global Admin is within your organization, you can find guidance on locating them here: How do I find my Microsoft 365 admin? - Microsoft Support.
3. Call Microsoft Support: For additional assistance, use this link to find the appropriate contact number: Global Customer Service phone numbers - Microsoft Support
4. **Contact a Reseller (if applicable):**If your Office 365 subscriptions are managed through a federated partner or reseller and the Global Admin cannot open a service request, they should contact the reseller’s support provider. The reseller can assist with initiating the request and coordinating with the Office 365 support team.

Note: If you’re an end-user, please coordinate with your Office 365 Global Administrator to handle these steps.Thank you very much for your valuable time and your cooperation.

Best regards,

Hoang-D - MSFT | Microsoft Community Support Specialist

Answer 2

Oddly enough, I had the exact same issue trying to achieve the exact same thing and switching to the legacy editor instead of the new one fixed it for me.

Answer 3

Yep I thought I was losing my mind, I second your solution

Answer 4

I've had other issues with the new editor, so that tracks. I'll have to give this a try. Thanks.