My game Super Head Soccer has been getting tons of config service errors recently. This has been causing servers to not load, with players being permanently kept in loading screens, since ConfigService is used as the source of truth for a lot of data and servers thus wait on the config to arrive to get the data. So while the graph below does not immediately suggest servers are waiting infinitely, I have personally had some accounts of mine be for large durations of time be put into servers that never finish loading, on every join and having to manually select a different server to test things, so I know infinite wait is a thing. In the future, we might rely less on ConfigService for important information and instead just restart servers. (EDIT: we have now removed all use of config service, at the very least temporarily.)
We use exponential backoff with jitter and a maximum retry wait time of 30 seconds and uncapped maximum retries when calling ConfigService:GetConfigAsync().
Seems related to this Async polls failing and being changed of their ratelimits again.
All HTTP requests started erroring with info on 1700 ratelimit on the server and 300 for client with HTTP inquiries after the above bug was fixed. Is this different for ConfigService?
Hi! Thanks for reporting. We have deployed a fix for this. Please check if this is resolved on your end and feel free to reach out if you encounter any more issues.
