Huh, that is strange! I wonder if its a quirk of the trigger system, or the way that I'm handling websocket messages.
I'll look into this! In the mean time, try using an "ordered switch" node between the calling trigger and the OBS triggers, that should execute each one in sequence and may mitigate the issue