Skip to content

Common issues

This page covers common issues you may run into and how to resolve them quickly.

This usually comes down to caching or integration timing.

Check the following:

  • If you’re using CDN delivery, your app may still be receiving cached data.
  • Clear your browser cache or test with a cache-busting query parameter.
  • Make sure your app is requesting the correct language code and format.

If you export files:

  • Confirm the exported files are included in your latest build.
  • Ensure your app is not falling back to an older bundled file.

Common reasons:

  • Some languages have empty values (empty values don’t count as strings).
  • Keys exist but haven’t been translated yet.
  • You recently removed a language or deleted keys.

Remember:

  • 1 key × 1 language = 1 string
  • History and previous values don’t count toward usage.

This often happens when:

  • You add a new language to a project with many existing keys
  • You bulk translate an entire language
  • You import a large file set at once

What to do:

  • Review usage in the workspace
  • Delete unused keys or languages
  • Upgrade your plan to continue adding strings

Auto-translate didn’t replace existing values

Section titled “Auto-translate didn’t replace existing values”

By default, auto-translate:

  • Generates suggestions
  • Does not overwrite saved values

If you expected replacements:

  • Ensure you selected “replace existing values” during bulk translation
  • Note that this option applies only to bulk translation, not per-key suggestions

This can happen if:

  • Your source file structure changed
  • Keys contain dynamic or inconsistent segments
  • Whitespace or casing differs between files

Recommendations:

  • Keep key naming consistent
  • Avoid embedding IDs or numbers in keys
  • Review import previews before confirming

Check:

  • CDN delivery is enabled for the project
  • The requested language code exists
  • The requested format/path matches your export settings

If the problem persists:

  • Try accessing the CDN URL directly in the browser
  • Confirm there are no typos or outdated URLs in your app

Deletions:

  • Remove all translation values immediately
  • Reduce string usage
  • Cannot be undone

If this happened in production:

  • Re-create the key or language
  • Re-import from a previous export or source control if available

If none of the above helps:

  • Check in-app support links
  • Include your workspace name, project name, and what you were trying to do
  • Screenshots or exact error messages help resolve issues faster

  • Getting started: revisit the setup steps
  • Auto-translate: understand suggestion vs bulk behavior
  • CDN delivery: caching and propagation details