Run cells and read outputs
Prerequisites
Section titled “Prerequisites”- Open a notebook with at least one code cell.
- Keep the notebook toolbar visible.
- Select a code cell and run it with the per-cell run control.
- Use Run cell & advance to execute and move forward.
- Use Run all cells to execute top-to-bottom.
- Read each cell’s output block for stdout, rendered output, or error content.
- If needed, use Stop execution, Restart kernel, or Restart and run all.
- Open the Problems panel to inspect notebook-related issues when errors persist.
- Re-run affected cells after fixes.
Verification
Section titled “Verification”- Executed cells show updated execution count and output blocks.
- Outputs appear under the correct cells, including errors when execution fails.
- Kernel state returns to idle after successful runs.
If Something Goes Wrong
Section titled “If Something Goes Wrong”- Cell stays queued or running
- Stop execution, restart kernel, and retry the run sequence in Executable cells.
- Import/module errors appear
- Check runtime package availability and rerun after installing dependencies in Notebooks.
- Outputs seem stale or out of order
- Run all cells from top to rebuild notebook state deterministically.
- Problem details are unclear
- Open the build log-style diagnostics surfaces (Problems and output sections) and inspect the full error text before retrying.