Need help fast? Chat with us at globalize.now — hit the chat icon on any page.
Re-scan shows "no i18n files detected"
If you trigger a re-scan and the globalize.now app shows "no i18n files detected", the job may already be running in the background — the UI is just not reflecting it yet.
There's a timing gap between when a job starts and when the app's status updates. The message can appear briefly while the job is processing. It doesn't mean the scan failed.
What to do: Wait a few minutes and refresh the page. Check your GitHub repo for a new pull request — that's the clearest sign the job ran successfully. If the issue persists after 10+ minutes, chat with us at globalize.now.
Job shows "Completed" but contains an error
If a translation job shows "Completed" status but you see a failed error when you click into it, the job likely partially succeeded — the strings were translated, but something went wrong at the commit or PR creation step.
What to do:
- Check your GitHub repo first. If a PR exists with the translated locale files, the translation itself worked. The error may be related to the repo connection, not the translation.
- If no PR exists, start a chat at globalize.now with your repo name and job ID.
Common cause: A GitHub authentication mismatch — for example, connecting globalize.now with one GitHub email while your repo is under a different account. Check that the GitHub account you connected has write access to the repo.
Translation job started automatically without my approval
If a translation job started without you explicitly triggering it, this is a known UX issue we're actively working on. Currently, connecting your repo to globalize.now and enabling auto-translate can trigger an immediate translation run.
How to avoid this going forward: Connect your repo but don't enable auto-translate until you're ready to start using billable translations. If you're on the free setup phase only (no billing connected), no translation job will run — only string extraction and locale file generation happen.
If a job ran and you weren't expecting it: Check your billing dashboard to see the character count used. If it's unexpectedly high, chat with us at globalize.now — we'll review the job and credit your account if appropriate.
What's coming: We're adding an explicit consent step before any billable action runs.