Why is my job stuck in “Processing”?
In Elovate, Processing does not necessarily mean the job is actively running in the background.
It usually means Elovate has finished its part of the work, but a manual action is still required before the job can move forward.
For example, in Content Enrichment, all data has been prepared, but items are waiting for you (or a moderator) to edit or approve them.
Important: While a job is in Processing, no API call to Magento has been made yet — the sync will only happen once the job is completed and approved (if moderation is enabled).
Common reasons for “Processing”
Manual moderation required – In Content Enrichment or Translations with moderation enabled, an editor or moderator must complete the items before they can be synced to Magento.
Job type workflow step – Some apps (like Content Enrichment) always have a manual step between generating/preparing data and syncing it.
Live/continuous rules – Content Enrichment and Translations with live rules keep adding new matching entities every ~15 minutes. The job stays in Processing until closed.
Errors blocking approval – Items with errors need to be fixed before you can complete the job.
How progress is displayed (per app)
Translations – May show a counter like 412/500 processed.
This is only for translations. Other apps do not display this counter.
Content Enrichment – Shows edited/total items (e.g., 1/424). All must be completed (and approved if moderation is enabled) before syncing.
Import/Export – Processing here may mean the file has been prepared but not yet triggered for sync or download.
How to troubleshoot
Check if a manual step is pending
For Content Enrichment: Go to My editor tasks or My moderation tasks and finish the items.
For Translations with moderation: Approve the translations before sync.
Check for errors
Open the job, filter for items with Error status, and fix them.
Continuous jobs
If using live rules, decide if you want to keep the job open or close it.
Synchronization Log (Apps → Synchronisation Logs)
Errors here are always Magento API errors — you can reproduce them via Postman and fix the cause.
Elovate-side errors (e.g., HTTP 500) should be reported to support.