Hi,
In my OutSystems environment, I'm getting a no healthy upstream error only in the Development environment, while the Test environment (identical architecture) works fine. It was working normally yesterday. What could be the causes for this sudden, environment-specific failure?
Hi @hava sh ,
Without access to investigate the issue directly, I would recommend reaching out to the support team. OutSystems Support.
Hi hava sh,
This error usually means that one or more front-end nodes in the Development environment became unhealthy or stopped responding to the load balancer. Even if Test shares the same architecture, it can still happen only in Dev due to:
A temporary service crash on one Dev frontend
Deployment/republish that left the node in an inconsistent state
Cache corruption or a stuck application pool
Infrastructure-level maintenance happening only on that environment
A quick set of checks you can try before contacting Support:
Restart the front-end services (or recycle the application pool if you have access).
Republish a small module (e.g., a blank app): this forces OutSystems to reinitialise parts of the environment.
Check Service Center → Monitoring → Frontends to see if any node is showing as unhealthy.
If the error persists, then it’s almost always infrastructure-level and only OutSystems Support can fix it, so raising a ticket is the right next step.
Hope this helps!