I've been using HTTP GET (rather than POST) so that my execution is paused while the subordinate flow I'm calling via GET is executed. (When I say subordinate flow, I'm talking about my API call to whatever slave process, which in my case is another Power Automate flow, but for you will be whatever API you're calling.) In my case, I want it to take as long as it takes. I used @Anonymous's method and I think it's working. For 30 minutes, I used a value of P0Y0M0DT0H30M0S, which is following the format detailed below.
Alternatively, you could use a POST, which will initiate that process and then continue executing in parallel without waiting, in which case you will need to find a way to poll the status of the subordinate flow (API call) to detect when it either finishes or fails, as @Jay-Encodian suggests.
Here's an excerpt from a site that I found listing the definition for that ISO 8601 duration format:
ISO 8601 duration format
ISO 8601 Durations are expressed using the following format, where (n) is replaced by the value for each of the date and time elements that follow the (n):
P(n)Y(n)M(n)DT(n)H(n)M(n)S
Where:
- P is the duration designator (referred to as "period"), and is always placed at the beginning of the duration.
- Y is the year designator that follows the value for the number of years.
- M is the month designator that follows the value for the number of months.
- W is the week designator that follows the value for the number of weeks.
- D is the day designator that follows the value for the number of days.
- T is the time designator that precedes the time components.
- H is the hour designator that follows the value for the number of hours.
- M is the minute designator that follows the value for the number of minutes.
- S is the second designator that follows the value for the number of seconds.
For example:
P3Y6M4DT12H30M5S
Represents a duration of three years, six months, four days, twelve hours, thirty minutes, and five seconds.
