Issue Overview
When adding new translation keys to Localazy, the following problem occurs:
-
Key upload succeeds -
Auto-translation works correctly (translated text is visible on the dictionary page)
-
Status remains untranslated on UI/CI
-
As a result, CI jobs fail
This workflow was functioning correctly previously, and the issue appeared recently without any changes to our configuration
Specific Symptoms
-
UI shows keys as "untranslated",but navigating to the dictionary page reveals translated text exists - Running
localazy downloadcommand treats keys as untranslated (translated text is not retrieved) - Status does not update even after waiting 3 days (retrying does not resolve the issue)
Note: In the attached screenshot, VAL99999 is a test key that was uploaded via code to verify this behavior.
# Example diff after running download command (CLI v2.0.8)
+ "NEW_KEY": "Original untranslated text" # Remains untranslated despite auto-translation
Attempted Solutions (Ineffective)
-
Switching to DeepL translation
-
Uploading via command line
-
Recreating automations
-
Running “CLEAR PROJECT DATA”
-
Manually deleting and re-adding languages
-
Checking plan limits
Workaround
Forcing status synchronization through manual UI operations works.
Steps
- Open the relevant project in Localazy
- Add a dummy key and immediately delete it
- Verify that the status has been updated in the UI
- Re-run the GitHub Actions job
-
localazy downloadshould now work correctly and retrieve translated text
Suspected Cause
There appears to be an issue with Localazy’s status synchronization process. While auto-translation completes successfully, the internal status update is not being triggered. Manual operations in the UI (adding/deleting keys) seem to force the status synchronization to execute.
Environment
- node: v22.18.0
- pnpm: v8.15.9
- Localazy CLI: v2.0.8
