Skip to main content

Error: 'Response status code does not indicate success: 502 (Bad Gateway) or 400 (Bad Request)'

What to do if you see a 502 Bad Gateway or 400 Bad Request error when running a FactoryMaster data import into Orchestrate.

Written by Arthur Ashdown

You may see one of these errors during a FactoryMaster data import when the Access API service on your server has stopped or is unresponsive. The service will need to be started or restarted from the Services console to restore the connection.


Restart the Access API service

To resolve this, your IT team will need to check and restart the Access API service from the Services console on your server.

📌Note: The service may appear as running in the Services console but still require a restart to function correctly.


Using MyDesk servers?

If you are hosted on our MyDesk servers, your IT team will not need to action this. Please raise a new case online and reference the title of this article so we can restart the service for you.

Did this answer your question?