.png)
Overview
A 502 Bad Gateway indicates that the backend service did not respond quickly enough or was temporarily unavailable.
It is a generic error and can occur for many reasons, not only in HCMS.
Typical Causes in HCMS Environments
A 502 reported against HCMS generally means:
-
The HCMS/Satellite instance did not respond within the expected time, or
-
The instance was unavailable at the moment of the request
One common scenario is:
High combined CPU and memory load → slow responses → Kubernetes marks the pod as unhealthy → pod restart → temporary 502s.
This is only one example; other infrastructure‑level issues can produce the same error
What to Check
When a 502 occurs:
-
Verify whether the issue is intermittent or consistent.
-
Check Satellite health (CPU, memory, restarts) if monitoring is available.
-
Confirm whether the issue affects all requests or only specific assets.
Checking Asset Size (Internal Recommendation)
If the issue occurs only for certain assets:
-
Open the asset in the Java Client or Web Client.
-
Review the binary size.
-
Assets larger than a few megabytes may require special handling, as they can cause slow processing or increased load.
There is currently no official maximum asset size documented; this guideline is based on observed behavior and is under internal review.
When to Contact Support
Please provide:
-
Timestamp(s) of the error
-
Endpoint(s) affected
-
Example asset ID(s), if relevant
-
Any available infrastructure or monitoring info (CPU, memory, restarts)