Hi,
I've set up a cloud flow in one of my environments that triggers manually on a specific record.
The first step it initializes a boolean variable and sets it to false. The flow then enters a "Do Until" stage, waiting for the variable to be set to true. Within this loop, a bound action is executed. This action returns a boolean value—true if it has completed its tasks or false otherwise.
The Issue
During testing, I intentionally created a large dataset to see if I could make the bound action time out—and I succeeded. However, when the action times out and receives the response below, it automatically retries and executes the bound action again. In my test, this happened three times before eventually returning true, allowing the cloud flow to complete successfully.
Interestingly, the "Do Until" loop itself only iterates once. The retries seem to occur within the execution of the bound action, not within the loop.
Another key observation is that the bound action appears to resume from where it left off, rather than restarting or reprocessing the same records.
My Question
Is this expected behavior when running a bound action from a cloud flow? It seems like a way to bypass the default two-minute timeout limit in Dynamics 365 CE online. I want to confirm whether this is an intended mechanism or if I should be handling it differently.
Bad Request from performing bound action from within the cloud flow:
{
"error": {
"code": "BadRequest",
"message": "Http request failed: the server did not respond within the timeout limit. Please see logic app limits at https://aka.ms/logic-apps-limits-and-config#http-limits."
}
}
Cloud Flow:
Thankful for all the input you guys have on this one!
Regards
