You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have a switch that triggers the execution of requests in sequence. In my example, I want to say something over multiple Sonos speakers using the sonos-http-api. Following sequence scheme is used:
[
"<Request1>",
"delay(4000)",
"<Request2>"
]
I am using the "multipleUrlExecutionStrategy": "series" and would expect that each request in the series is only executed once. However, when the switch is triggered, Request1 is executed twice, once immediately and once after the delay. Request2 is executed after the delay time, so that both requests are executed simultaneously after 4s. Am I misunderstanding the series with delays concept or is this a bug?
I would like to have a switch that triggers the execution of requests in sequence. In my example, I want to say something over multiple Sonos speakers using the sonos-http-api. Following sequence scheme is used:
I am using the
"multipleUrlExecutionStrategy": "series"
and would expect that each request in the series is only executed once. However, when the switch is triggered, Request1 is executed twice, once immediately and once after the delay. Request2 is executed after the delay time, so that both requests are executed simultaneously after 4s. Am I misunderstanding the series with delays concept or is this a bug?Version
Actual Configuration
The text was updated successfully, but these errors were encountered: