Notebook troubleshooting
Common problems
Section titled “Common problems”| Symptom | Likely cause | What to do |
|---|---|---|
| Notebook stuck in “creating” / will not start | Project quota exhausted, or cluster capacity busy | Check quota in the dashboard; stop unused notebooks to free quota; retry |
| Cannot open JupyterLab after launch | Session still starting | Wait a few seconds and reconnect from the dashboard |
| Files missing after a restart | Files saved outside /home/jovyan |
Only the home directory on your workspace volume is persistent; keep work under /home/jovyan |
| Package missing after restart or image change | Package environment follows the image, not the volume | Reinstall the package (keep a requirements file on your volume); custom images are not currently available |
| Notebook stopped by itself | Idle timeout (30 min) or max session length (24 h) | Start it again from the dashboard; nothing on your volume is deleted |
| GPU profile unavailable | GPU requires an entitlement | See Compute profiles |
Known platform limitations (verified 2026-11-10)
Section titled “Known platform limitations (verified 2026-11-10)”- No automated backup of workspace volumes. Keep your own copies of critical data (see Workspace storage).
- GPU self-service entitlements are not offered at launch. GPU capacity is reserved behind an entitlement model; see Compute profiles.
- Orphaned volumes from deleted notebooks can linger in a workspace until a retention policy is finalized. They do not affect quota beyond their size, and support can help clean them up.
- Per-project default resource limits (so a misconfigured workload cannot exceed the namespace ceiling) are being completed as part of the public launch hardening.
Getting help
Section titled “Getting help”If a problem persists, contact the support channel provided with your account and include: your project name, notebook name, approximate time (with timezone), and what you already tried. Never share passwords or verification codes — support will not ask for them.
Platform-level known issues tracked for the release are reflected on this page as they are verified; sections above marked verified reflect tested behavior, not plans.