Skip to main content

Saving and running the translation job (legacy)

Legacy: running the old translation jobs. For new work, see Running workflow actions.

Once you’ve configured your translation job in Elovate — including entity type, languages, rule builder conditions, and selected attributes — the final step is saving and running it.


1. Review your job settings

Before saving, double-check:

  • Entity type – Products, Categories, CMS pages, Attributes, or Magefan blog posts.

  • Source and target languages – Make sure the correct languages/locales are selected.

  • Rule builder filters – Confirm you’re translating only the intended items.

  • Glossary usage – Ensure the correct glossary is applied to preserve brand terms.


2. Saving the job

  • Click Save translation job.

  • When saved, the job will appear in your Translations → Jobs list.

  • The job status will initially be New.


3. Running the job

Manual start

  1. Open the saved job.

  2. Click Run job to start translation immediately.

Automatic start

  • If you enabled Automatically translate during setup, the job will start as soon as it’s saved.


4. Job statuses explained

As the job runs, you’ll see different statuses:

  • New – Job is saved but not started.

  • Queued – Job is waiting in line to start.

  • Processing – Translation is in progress.

  • Generating – AI or translation provider is producing content.

  • Done – All items have been processed.


5. Moderation and auto-sync

  • If Auto-sync is disabled, translated content will wait for moderator approval before being pushed to Magento.

  • If Auto-sync is enabled, translations are automatically sent to Magento as soon as they’re complete.


6. Tips for running translations smoothly

  • For large jobs, consider running during low-traffic hours to reduce API strain.

  • Keep an eye on notifications in the job view for translation errors (e.g., GPT token limits or provider issues).

  • Use Continuous translation if you want the rule builder to keep adding new matching items over time.

Did this answer your question?