Asynchronously execute http requests under a multi shortcut

[ritiek]

Is your feature request related to a problem? Please describe.

Hi, I've been using HTTP Shortcuts to control few devices on my local network and it works really well.

However, I've noticed HTTP requests are fired synchronously when executing a multi-shortcut, which makes the http shortcuts at the end of a multi-shortcut to take a while before they are fired off. Also when one of my network devices is offline, it seems to keep waiting to establish connection with this offline device (circle keeps spinning) for a couple of seconds and the http requests that are yet to be fired off (for actually online devices) get delayed due to this.

Describe the solution you'd like

I think firing multi-shortcuts asynchronously should help with both these, but wasn't able to find anything about it in the app. Async should help with http shortcuts getting executed simultaneously and also it shouldn't be an issue whether some device on my network is offline.

Describe alternatives you've considered

I think creating advanced workflows using javascript could help here (haven't tried them yet), but if possible I feel a native option in app to make http requests in async would be nice.

Additional context

I'm using HTTP Shortcuts v3.9.0. Thanks!

[Waboodoo]

Thanks for the details.
The ability to run HTTP requests in the background or asynchronously is one of the main things I want to bring into the app, but unfortunately it also requires quite some work and I currently don't have much time for this project. I'm hoping to make some progress on this topic within the new few months but can't make any promises.

[PureIncompetence]

I'd like to second this feature request. When using HTTP Shortcut to switch on multiple wifi light bulbs simultaneously its kind of irritating to see them lighting up one by one with a noticable delay even without one of them being offline/unreachable.

[Waboodoo]

As of version 3.28.0, this is somewhat possible. If possible, shortcuts will run in headless mode. If all of the shortcuts triggered by the multi shortcut support it, they will be executed asynchronously, in the sense that the will be triggered one after the other but without waiting for the responses. This should at least partially improve the issue here.