The Synchronisation Log in Elovate is your central hub for tracking all data pushes to Magento and seeing exactly what happened during each sync. It records every success, warning, and error, making it essential for troubleshooting and verifying that your jobs are working as expected.
1. Where to find it
Go to:
Apps → Synchronisation Logs
You’ll see a chronological list of all sync events across imports, exports, translations, and content enrichment jobs.
2. What you’ll see
Each log entry typically contains:
Date & time of the sync attempt
Entity type (e.g., product, category, CMS page)
Entity ID / SKU
Job name the sync came from
Status (success, warning, error)
Error message (if applicable)
3. How to use it for troubleshooting
A. Identify problem entities
Sort or filter by status: Error to see only failed sync attempts.
Click the entity name/ID to go directly to the source item in Elovate.
B. Understand Magento API errors
Important: Synchronisation Log errors are always Magento-side errors.
These can be reproduced by sending the same request to Magento via Postman.
This means you can usually fix them yourself by:
Creating missing attributes or options in Magento
Adjusting incorrect data values
Ensuring required fields are filled
C. Differentiate between slow and failed jobs
A job showing 85/100 completed doesn’t always mean 15 errors — sometimes those 15 are still processing.
If the remaining items take a long time with no change, they may indeed be stuck with errors.
Click into the job to confirm.
4. When to contact Elovate support
If the error message is unclear and you cannot reproduce it in Postman, it may be an Elovate-side issue (e.g., a
500error).Provide the job name, affected entity IDs, and the log excerpt when contacting us — this speeds up resolution.
5. Best practices
Check logs regularly when running large or recurring jobs.
Filter by job name if you only want to see sync attempts from a specific process.
Act quickly on repeated errors to avoid a backlog of failed entities.