5 Replies
This only happens when connecting to a remote prod server (atl was the one I was using). The error doesn't occur on a local test run.
does it consistently occur with only the third client?
Yes, as well as the 4th+
It seems to also happen sometimes on the very first client connecting causing a server to spin up
ill open a ticket for this on our end, sorry we dont have the time to help out directly
np