If your Magento store is temporarily offline or unreachable while Elovate tries to sync, the sync for that job or item will fail.
This can happen if your Magento server is down for maintenance, your API credentials are invalid, or there’s a network timeout.
1. What you will see in Elovate
In the job view, affected items will show the Error status.
In Apps → Synchronisation Logs, you’ll see Magento error messages such as:
Could not resolve host503 Service UnavailableConnection timed out
These messages are straight from Magento and mean Elovate could not deliver the update.
2. What happens to your data
No changes will be pushed until a successful sync is made.
The data remains safe inside Elovate — you can retry pushing the failed items once your Magento store is back online.
3. How to fix and retry
Check if your Magento store is accessible via browser or API.
If offline, wait until your hosting provider or tech team confirms it’s back up.
Once online, go back to Synchronisation Logs or the job view and retry the failed items.
If the issue was due to incorrect API credentials, update them under:
General Settings → Settings → Integrations → Edit Magento Store.
4. Best practices to avoid sync failures
Schedule big sync jobs outside of your Magento maintenance windows.
Use smaller, more frequent exports or enrichment pushes instead of one massive sync.
Monitor the Synchronisation Log regularly to catch failures early.