Minimum Version Required: 26.01
Pre-Conditions
You must be logged in as an administrator or have the necessary permissions to access application settings and cache management tools.
The application must have localization or multi-language features enabled.
You must know the expected language identifier and tenant routing key for your specific environment.
Steps
Refresh the Cache: Clear your application cache or force a hard refresh (Ctrl + F5 or Cmd + Shift + R). A stale cache state is a common cause after recent localization or translation updates.
Verify Language Identifiers: Navigate to your user or tenant settings and confirm that the assigned language identifier (e.g., 'en-US') is correct and supported by your environment.
Check Routing Keys: Ensure that the tenant routing key is appropriately configured and active for your session.
Inspect for Case Sensitivity: If you recently customized any tables or look-up keys, check your configurations to ensure there are no case mismatches (e.g., typing "Translation" instead of "translation"), as database lookups are often case-sensitive.
Verify Initialization Data: If this is a new environment or following a major update, verify in your setup logs that the seed or initialization data for translations was successfully applied.
Contact Support: If the issue persists after attempting these steps, please contact our support team. To ensure efficient troubleshooting, please gather and provide the following specific information:
Exact error messages or codes encountered (including the specific table or text string failing to translate).
Screenshots or video recordings of the issue.
Log files (specifically application error logs and browser console network logs).
The exact steps taken by the customer that led to the issue.
The date and time the issue was first observed and any recurrence.
Any changes made to the system before the issue appeared (e.g., recent software updates, custom field additions, or cache clearings).
Fields And Definitions
TableTranslation: A database table or system function responsible for storing and retrieving localized text strings to display in the user interface based on the user's selected language.
Language Identifier: A standardized code (such as 'en-US' for US English or 'es-MX' for Mexican Spanish) used by the system to fetch the correct language data.
Tenant Routing Key: A unique digital identifier used in multi-tenant architectures to ensure that data, configurations, and localizations are routed to the correct customer workspace.
Seed/Initialization Data: Base data that is automatically loaded into a database during the initial setup of an environment (e.g., default language packs and essential configurations).
Stale Cache State: A scenario where the application serves outdated, temporarily stored data instead of fetching the newly updated translation rows from the live database.
Best Practices
Consistent Naming Conventions: Always use consistent casing (e.g., entirely lowercase or camelCase) for table names and look-up keys to prevent case mismatch errors.
Post-Update Cache Clearing: Make it a standard administrative practice to clear the system cache immediately following any updates to localization files or data schemas.
Staging Environment Testing: Test new translation strings and initialization data in a staging environment before deploying them to production to ensure seed data applies correctly.
Audit System Changes: Keep a log of any changes made to language identifiers or tenant routing keys to quickly pinpoint misconfigurations when "not found" errors occur.