Troubleshoot the IDE¶
Identify where the failure occurs: the console manages accounts and environments, the notebook kernel executes code, and the Jupyter extension handles canvases and displays. Keep the failing step and original message before retrying.
| Symptom | Check first | Next step |
|---|---|---|
| Sign-in or verification code fails | Account availability, password and verification code | Refresh the code; ask an administrator to reset a forgotten password |
| Environment creation is unavailable | Maximum profile and retained limit | Ask the administrator to check access and profiles; stopping does not release a retained slot |
| Environment remains waiting | Concurrent limit and the explanation on its card | Stop unused running environments; ask for a machine-capacity check if needed |
| Open IDE creates no usable tab | Running state and popup blocking | Allow popups for the site and enter again from the console |
| Access denied or session expired | Password changes, account status or permission changes | Sign in again through the console; do not use another person's workspace URL |
| Digital/Analog buttons are missing | Active notebook and enabled extension | Locally, run jupyter labextension list; ask the operator to check a hosted image |
ModuleNotFoundError |
Kernel interpreter and installed packages | Run the version check and select the intended kernel |
| An operation or attribute is unavailable | SDK/companion compatibility | Compare the version notes, keep the exception, and ask the maintainer |
| Bokeh is blank or reports a version error | Python Bokeh versus the bundled BokehJS | Restore a matching combination rather than upgrading one side alone |
| Canvas changed but output did not | Whether code was only synchronized; stale result status | Execute the generated cell or select Run in the editor |
| Detached appears | Manual edits or deletion of a generated cell | Keep the original code and select “生成到新单元格” |
| Variables disappear after a restart | Whether state existed only in memory | Rerun definition cells or load exported result files |
| Saving or writing fails | Disk allowance, workspace path and permissions | Export what you can, check usage, and avoid repeating large runs |
| Code is unavailable | Installed code-server and terminal permission | Follow upstream local setup instructions or ask the platform operator |
A job keeps running¶
Check simulation size, shots, time steps and resource limits. The resource-budget guide explains how to estimate cost before scaling up. An atom count accepted by the editor does not guarantee sufficient simulation memory.
Cancellation is a request, not proof of immediate termination. Read the actual terminal job state. Interrupting or restarting the kernel may be necessary, but discards variables in memory. Save files before considering an environment stop. For an offline machine, ask the administrator to recover its access; deleting the environment cannot recover files.
Include useful information in a report¶
- Page, steps, time and environment ID.
- Python, CASCAQit, CASCAQit-Jupyter and Bokeh versions from the active kernel.
- Original error, diagnostic code and the smallest reproducing code sample.
- Expected and actual results; for editor behavior, a screenshot with sensitive details removed.
Exclude passwords, tokens, entry tickets, full authentication requests and notebooks containing sensitive output. For numerical or SDK API issues, continue with SDK troubleshooting.