When something goes wrong with your workspace

OpenShift Dev Spaces Cloud Development Environments can encounter startup failures, runtime errors, and IDE issues. Start by checking logs, then use the symptom-based sections in this guide to diagnose and resolve the issue.

The first step for any problem is to check the Cloud Development Environment logs. Logs capture IDE extension activity, container events, and process errors that point to the root cause.

Table 1. What problem are you experiencing?
Symptom	Description
Need to check logs	View logs from the CLI or the editor to identify errors and warnings.
Cloud Development Environment is slow	Tune CPU and memory resource limits in your devfile to improve runtime performance.
Webview or editor UI errors	Fix service worker errors in private browsing windows.
Devfile syntax or validation errors	Diagnose component failures, lifecycle command problems, and volume or endpoint misconfigurations.