Unfortunately, the use of buttons is not self-sufficient, although it can be very helpful in certain cases. If the session is interrupted, the cycle will also be interrupted. I haven’t found a way to restart an interrupted automation cycle. You can enable cycle activation by manually pressing another action button that runs external scripts. However, the downside here is that the button’s status will remain frozen until the cycle finishes. In other words, it should be a one-time action, but you’ll have to return to it if deactivated. The frequency of such actions is a big question. Overall, there are many vulnerabilities in this approach. This mechanic is suitable only for a continuous session during a specific scenario.