Guard platform actions with connection state
Check that a service is connected before you act on it, so a dropped connection fails quietly.An OBS scene switch or a Spotify skip assumes that service is actually connected. If it dropped a moment ago, the action fails partway through your flow and leaves it in a half-run state.
Read Connection State first and branch on it: run the action when the service is up, and take a quiet fallback (a log line, a short chat notice) when it is down. The flow stays predictable even when a platform blinks out.
For flows that should react the moment a service drops or comes back, start them from the connection triggers instead, such as On Connection Lost and On Connection Restored.