Automation cancelled when two triggers flip simultaneously and mode is restart and the automation is already running (reproducible) about core

[bdraco]

probably fixable by removing

core/homeassistant/helpers/script.py

Line 1765 in 6c15351

await asyncio.sleep(0)

but that will reduce the loop production

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (automation) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of automation can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign automation Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

automation documentation
automation source
_{^{(message by IssueLinks)}}

[TheJulianJES]

I'll need to check later, but this looks like the same issue as this one:

• #118638

[zanna-37]

It's slightly different but I think it has the same root cause.
My automation is a little bit simpler to reproduce.

Sorry I didn't find that issue before opening this one.

[LucasCZE]

This is interesting. It looks like the same issue I have created (the other issue mentioned by TheJulianJES). But I have a lot of automations that would fail if this issue could be reproduced in my environment. An automation must have at least 3 triggers to fail in my environment. But I am running 2024.5.5, so I think this is a new, even worse, behavior in 2024.6.0.