@ShadowWizard I fixed the throttle logic that could lead to a situation that it stayed in being throttled mode (and thus not posting anymore) (that was what we saw earlier this week). I also changed the websocket failure handling and added the actual code that was needed to successful re-establish a websocket connection.
I tested in the sandbox with a debugger attached once I figured out how I had to configure the ssh tunnel and chrome dev tools. I happened to be able to trigger that throttle error so I could easy diagnose.
