Summary:
If your Unity Remote Config dashboard is slow, freezing, or returning 502 errors—especially when editing or updating overrides with large JSON payloads—it may be due to having too many Game Override campaigns (including inactive ones) in your project. This article explains how to work around the issue by using the API or CLI for updates and deleting unused Game Overrides to improve performance.
Procedure:
- Overview
- Workarounds
- How to Delete Old Game Overrides
- Additional Resources and Support
Overview
When a project has a large number of Remote Config campaigns (active and inactive), updating or enabling overrides can cause performance issues such as freezing or 502 errors. This happens because the backend checks every Game Override campaign’s schema during these operations, and the process slows down as the number of campaigns increases.
Workarounds
To alleviate or resolve these issues, try the following workarounds:
-
Use the Remote Config API or CLI:
- Making updates through the Remote Config REST API or the Unity CLI tool can be more reliable, especially for large payloads or when the dashboard is unresponsive.
-
Delete Unused or Inactive Game Overrides:
- Reducing the total number of Game Override campaigns (especially inactive ones) can significantly improve performance. This decreases the complexity of backend schema checks and may resolve the issue completely.
How to Delete Old Game Overrides
- Log into the Unity Cloud Dashboard.
- Navigate to your Game Override service.
- Review the list of campaigns.
- Identify and delete campaigns that are no longer needed (especially those marked inactive).
Additional Resources and Support
- Refer to the Remote Config REST API documentation for instructions on updating overrides and managing campaigns via API.
- Refer to the Unity CLI tool documentation for command-line options to manage Remote Config data.
- If issues persist after following these steps, contact Unity Support for further assistance.