-
Support
- 502 Bad Gateway - Slow Power Pick Connection
-
Account & Licensing
-
Installing & Updating
-
Power Pick Connections
-
Data Push & Data Pull
-
API
-
Reports
-
Snapshots & Dashboard
-
Workflows
502 Bad Gateway - Slow Power Pick Connection
Issue:
temPath tries to reach your Power Pick system, but the connection "times out" because the response was a bit too slow, resulting in a 502 Bad Gateway error.
Resolution:
Check that your Power Pick service is active and your network is stable—sometimes a quick restart or breaking large tasks into smaller batches is all it takes to get things moving again.
A 502 Bad Gateway error is essentially a communication breakdown. This type of error can happen for several reasons, one of which is a communication gap between ItemPath and Power Pick.
Think of it like this: ItemPath sent a request over to your Power Pick system to grab some data, but Power Pick took too long to answer.
Because Power Pick runs on a local server at your facility, this error usually points to a temporary "hiccup" in the connection between ItemPath and your local hardware.
Common Causes of Slowness
If your Power Pick connection is dragging, it’s usually due to one of these three things:
- Server Congestion: The computer running Power Pick might be busy with a backup, software updates, or other heavy tasks that are hogging its resources.
- Network Lag or VPN Drops: If ItemPath connects to your system via a VPN or a specific gateway, a momentary dip in your internet speed or a VPN disconnect can cause a 502 error.
- Database Congestion: Sometimes asking for too much data at once (like a massive sync) can cause the local system to "hang" while it processes the request.
Recommended Next Steps
Because the 502 error occurs on the local side of the connection, ItemPath doesn't have direct access to fix it. Here is the best way to get things moving again:
- Check with your Internal IT Team: Your IT team can verify if your local server is running smoothly, check for any network outages, and ensure the VPN (if you use one) is active. They can also check if the Power Pick integration service needs a quick restart.
- Contact Kardex Support: If your network is healthy but Power Pick is still responding slowly or not at all, the Kardex support team is the best resource to help optimize your Power Pick database or service settings.
- Try Smaller Batches: If you are currently pushing a very large amount of data, try breaking it into smaller "chunks." This can sometimes help a struggling local connection keep up without timing out.
Need the technical details for your IT team?
You can view the specific timing and error logs in ItemPath under the API Calls or Logs section. This information can be very helpful for your IT or Kardex support representative to see exactly when the connection is dropping.