When you create a job in Elovate (Import, Export, Translation, or Content Enrichment), the first step before anything runs is validation.
Validation checks if your job setup, rules, and data are correct before the system starts processing.
If a job appears to be stuck on Validating, it usually means Elovate is still checking:
That all required fields are filled
That your filters/rules return valid entities
That your file structure (for imports) matches the expected format
That your source and target attributes/languages are supported
That the connection to Magento and/or external providers (e.g., ChatGPT, DeepL) is working
Common reasons for slow or stuck validation
Large dataset
If your rules return thousands of products, categories, or pages, validation may take longer to compile the full list.
Complex filters
Multiple groups, conditions, or “IN” rules with many values can slow validation.
File validation issues (Imports)
Incorrect headers, unsupported file type, or mismatched delimiter will prevent validation from completing.
External provider checks
Translation jobs may need to confirm your API connection to DeepL or ChatGPT before moving forward.
Magento API delays
If your store’s API is slow to respond, validation will take longer since Elovate must check data against Magento.
How to troubleshoot
Reduce initial scope
Test with a smaller rule set or fewer SKUs to confirm the job runs, then expand.
Check file format (Imports)
Compare your file with the example template provided in Elovate. Ensure headers and data types match exactly.
Check Magento connection
Go to General Settings → Settings → Connections and ensure your store connection is valid.
Check external integrations (Translations & AI)
Verify that your DeepL or ChatGPT integrations in General Settings → Settings → Integrations are active and working.
Look for error notifications
Sometimes a job in “Validating” actually failed but hasn’t moved to “Error” yet. Refresh the page and check your Synchronisation Log for more details.
Tip
If validation takes more than a few minutes for a small dataset, it’s likely there’s a file structure or connection issue rather than just slow processing. Fix the root cause before retrying.