Overview
During scheduled maintenance activities on HCP Boundary, users may occasionally observe minor abnormalities in behavior or connectivity — even though the official status page may indicate minimal expected disruption and the HCP Boundary cluster itself reports a healthy state.
These disruptions are typically brief and self-resolving but may momentarily affect the user interface or worker connectivity.
Symptoms
- UI not responding as expected
- Difficulty initiating or authorizing sessions
- Boundary CLI or UI may appear stuck or need re-authentication
- Worker nodes (self-managed) temporarily unable to proxy sessions
Cause
These temporary behaviors are observed during scheduled platform upgrades or maintenance performed by HashiCorp on HCP Boundary infrastructure. While such activities are designed to be non-disruptive, some short-lived inconsistencies may still be seen in edge cases.
Workarounds
If you experience minor disruption during maintenance, try the following:
-
Browser UI not responding properly?
🔁 Simply perform a hard refresh in your browser. -
Worker nodes not proxying sessions?
🔄 Restart the Boundary service on each of your self-managed workers:systemctl restart boundary
Additional Notes
- These disruptions do not indicate a permanent failure or configuration issue.
- Your HCP Boundary cluster will continue to show a healthy status throughout.
- Maintenance activities are always published ahead of time on the HashiCorp Status Page, including expected impact levels.
When to Contact Support
If the issue persists after performing the above workarounds or is observed outside of the maintenance window, please reach out to HashiCorp Support here with:
- Timestamp of the issue
- Logs from the worker(s).
- UI error message or behaviour description