Overview
When a job in Elovate (import, export, translation, or content enrichment) runs into errors, you can often identify and fix them yourself.
Here’s a structured approach to troubleshooting.
1. Locate the errors
From the job view:
Go to Apps → [App Name] → Jobs.
Click the job name to open it.
Filter for entities with Status: Error.
From the synchronisation log:
Go to Apps → Synchronisation logs to see all sync attempts and detailed error messages.
2. Identify the error type
Elovate errors generally fall into two categories:
A. Magento API errors
Origin: These come directly from Magento.
Examples:
“Attribute value is not valid”
“Category ID not found”
“Stock source missing”
How to troubleshoot:
Reproduce the request in Postman to confirm the error.
Fix the data/config in Magento (e.g., create the missing category, correct the attribute value).
Retry the failed entity in Elovate.
B. Elovate-side errors
Origin: Elovate’s processing logic or AI integrations.
Examples:
500 internal server error
GPT token limit reached
Provider API timeout
How to troubleshoot:
Check if the issue is related to AI settings (e.g., add GPT tokens in General settings → Integrations).
If not fixable from your side, contact Elovate support — we can resolve system-side issues.
3. Common error scenarios & fixes
Error message | Likely cause | Solution |
“Attribute value is not valid” | Trying to set a value that doesn’t exist in Magento | Add the missing attribute option in Magento or during import |
“Category ID not found” | Referencing a non-existing category | Create the category in Magento first |
“Stock source missing” | Stock attribute references an unavailable source | Create the source in Magento or remove it from your data |
GPT token limit reached | AI credits used up | Add more tokens in General settings → Integrations |
API timeout | Temporary delay in provider response | Retry after a few minutes |
4. Retry after fixing
Once you’ve corrected the root cause:
Go back to the job view.
Select the failed entities.
Click Regenerate (or Retry for non-AI jobs).
Confirm they complete successfully.
5. When to contact support
You’ve confirmed it’s not a Magento API error.
You’ve retried, but the issue persists.
You see unexplained Elovate-side errors like
500or data not saving.