Open OleksandrBerchenko opened 4 years ago
Hey there @home-assistant/core, mind taking a look at this issue as its been labeled with an integration (script
) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
Problem exists
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
The same here, i don't know why, delay doesn't work properly
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
I am running into this as well. @OleksandrBerchenko - did you find a workaround?
Not really. Just tried to rewrite my scripts to avoid this situation.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still actgual
On Sat, Dec 30, 2023 at 6:05โฏPM issue-triage-workflows[bot] < @.***> wrote:
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
โ Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/40237#issuecomment-1872622901, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMBUT7VB6W44IUMEMJZ5U5TYMCM5NAVCNFSM4RR47JXKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGI3DEMRZGAYQ . You are receiving this because you commented.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment ๐ This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, it's still actual!
@OleksandrBerchenko
This seems like expected behavior to me.
Run the scripts in parallel mode.
https://www.home-assistant.io/integrations/script/#script-modes
The problem
Imagine the following scripts:
If I just run
script_d
, then everything works as expected: all three "child" scripts are triggered andscript_d
finishes,script_a
andscript_c
finish in a moment andscript_b
finishes in two minutes.Now let's run
script_b
first, wait for a few seconds and then runscript_d
. As expected, whenscript_d
triggersscript_b
, nothing happens. because the script is already running:But instead of continuing to the next step,
script_d
hangs and starts to wait until the previous run ofscript_b
finished! See the log below.Environment
Problem-relevant
configuration.yaml
n/a
Traceback/Error logs
Additional information
n/a