Dashboard translation inconsistency following deployment
Summary
Following a deployment on April 3, 2026, parts of the customer dashboard displayed raw translation keys instead of localized text. Functionality remained available, but the user experience was degraded.
What Happened
On April 3, 2026 at approximately 11:11 UTC, a translation deployment was triggered in connection with the rollout of new features. The deployment process replaced the frontend locale files entirely with data sourced from the translation database, which did not contain all translation keys required by the frontend.
As a result, a significant number of translation keys were removed from the frontend locale files. This caused raw translation key identifiers to appear in the user interface instead of the intended localized text.
Translation data existed across multiple sources that were not fully synchronized. The deployment function built locale files exclusively from one source, discarding keys maintained elsewhere.
No customer data was affected. All platform functionality remained fully operational throughout the incident. The issue was strictly cosmetic, affecting the display of UI labels and descriptions.
Impact
Users of the customer dashboard experienced degraded presentation across multiple sections. Navigation labels, form fields, modal dialogs, service descriptions, and status messages appeared as internal key identifiers rather than readable text. The impact was most visible on recently updated pages including storage, IP Intelligence, Redis management, and the main dashboard overview. No data was lost and no functionality was impaired.
Actions Taken
The locale files were restored from the last known good state within minutes of investigation completing. New translation keys introduced by the feature rollout were merged back into the restored files. All five language files were verified against the complete set of translation references used by the application. A full validation confirmed that all required translation keys were restored. The frontend was rebuilt and restarted at 15:57 UTC.
Preventive Measures
The translation deployment function has been permanently changed from an overwrite model to a merge model. The new process reads the existing locale file from the frontend server before making any changes, creates a backup copy, and then merges updates into the existing data. Keys that exist in the locale file but not in the source database are preserved. No deployment can remove existing translation keys. Additionally, automated validation of translation completeness has been recommended as a build pipeline step to catch missing keys before they reach production.