Summary
Large numbers of Overrides—especially disabled or outdated ones—can make the Overrides list slow to load and, in some cases, show as empty or return HTTP 500 errors in the Dashboard/Admin API. Clients typically continue to receive the correct configuration, but you may temporarily lose UI/API access to manage Overrides. Regularly deleting unused Overrides and keeping payloads small improves performance and reduces the risk of timeouts.
Description
The Overrides list view aggregates and returns all Overrides for an environment. When an environment accumulates many entries (including big configs and disabled Overrides), listing can become slow and may intermittently fail. While the listing UI/API may be affected, the delivery of Overrides to clients generally remains intact.
Notes
- These incidents are often due to long-running list requests. They usually resolve on their own as requests complete.
- There’s nothing actionable on the client side while a pod is stuck. If needed, Support can restart pods or deploy more pods to restore responsiveness.
- Unity currently does not enforce a hard limit on the number of Overrides per environment, so operational hygiene is important.
Common symptoms
- Empty Overrides page in a specific environment.
- HTTP 500 errors when listing Overrides via Dashboard or Admin API.
- Direct links to individual Overrides still open (and can be edited).
- Clients continue to receive the expected Override content.
Likely causes
- A large number of Overrides in the environment (including disabled/archived ones).
- Very large payloads (“big configs”) increasing response size/time.
- Transient backend conditions (long-running list requests, pod hangs, temporary service spikes).
Impact
- Temporary loss of UI/API visibility and management for Overrides.
- No immediate impact on client delivery; players typically continue to receive correct configurations.
Recommended actions
- Clean up unused Overrides:
- Delete disabled or obsolete Overrides to reduce list size.
- If the list view fails, use known direct links to open and remove large/disabled entries.
- Reduce payload size:
- Break very large configurations into smaller logical Overrides.
- Move static/bulky data into Remote Config keys or other stores when appropriate.
- Organize by environment:
- Keep experiments and temporary Overrides in dev
If all else fails, please reach out to our Support team to get your Game Overrides dashboard up and running again.