Skip to main content

E66 — WS_TAGGED_SUBSCRIBER_FAILED

Getting a subscriber on the TAGGED_RETURN channel failed while waiting for a server response.

What happens​

The error is logged once per boot, the task waits 500 ms, and then retries getting the subscriber in a loop. Requests that require a tagged response (e.g., solve submissions) are blocked until a subscriber is available. The WebSocket connection itself is not affected.

Possible causes​

  • All subscriber slots on the TAGGED_RETURN PubSubChannel are occupied — too many concurrent requests are waiting for responses simultaneously.
  • A firmware bug caused the channel to reach its subscriber limit.

How to fix​

  1. Wait — The retry loop resolves this automatically once a subscriber slot becomes free.
  2. Reboot the device — Resets all channel state.
  3. Contact support — Open an issue on GitHub if this appears consistently during normal competition use.