Need help fast? Chat with us at globalize.now — hit the chat icon on any page.
Job shows "Failed"
A failed job shows its error in the project dashboard and can be retried from there. The usual causes:
- Repository access. The Git account you connected no longer has write access to the repo, or the repository connection was revoked. Reconnect it under Project → Settings → Repository.
- Credit ran out. Translations pause and the app tells you why. Top up or upgrade under Settings → Billing, then retry the job. See How is billing calculated?
- Budget limit reached. If you set a monthly limit under Project → Settings → Budget, jobs are rejected once it's hit — raise the limit or wait for the next month.
If the error isn't one of those, chat with us with your project name and job ID.
Re-scan shows "no i18n files detected"
If you trigger a re-scan and the app shows "no i18n files detected", the job may already be running in the background — the status just hasn't updated yet.
What to do: wait a few minutes and refresh. Check your repository for a new pull request — that's the clearest sign the job ran. If nothing changes after 10 minutes, check the locale path patterns in project settings match where your locale files actually are, then chat with us.
Job shows "Completed" but contains an error
The job likely partially succeeded — the strings were translated, but something went wrong at the commit or pull-request step.
- Check your repository first. If a PR exists with the translated locale files, the translation worked and the error is about the repo connection.
- If no PR exists, chat with us with your repo name and job ID.
Common cause: an account mismatch — globalize.now connected with one GitHub or GitLab account while the repo belongs to another. The connected account needs write access to the repository.
A translation job ran when I didn't expect it
Jobs start on three triggers, all of them settings you control:
- Pushes to watched branches — Project → Settings → Repository → Watched branches. Remove a branch from the list and pushes to it no longer start jobs.
- Translate pull requests — if it's on, new strings in a PR are translated onto the PR branch. Turn it off, or turn on Skip draft pull requests, if you want to control the timing.
- Manual jobs you run from the dashboard.
The first job after connecting a repo translates everything that's already there, which is the largest job you'll see. To cap spend, set a monthly limit under Project → Settings → Budget: jobs are rejected, not silently run, once it's reached.
If a job ran and the cost surprised you: Settings → Billing shows what each job cost per language. If something looks off, chat with us with the job ID — we'll review it and credit your account if appropriate.