Run, interrupt and restart the kernel

App version: 1.0.1iPad · iPhoneContent checked: 2026-09-21Screenshot UI: EnglishStandard / Pro

What you will do

Understand execution order, stop a long task, and start with a fresh Python state.

Before you start

• An active Standard or Pro subscription, or an eligible trial.

Download the tutorial workspace

Where to start

Open a notebook → execution controls

Keep in mind

On iOS/iPadOS 1.0.1, completely close and reopen Vibeit after changing Environment settings. Restart Kernel clears the Python session but does not reload these saved settings.

Follow the steps

1. 1Run the current cellRun a cell when it is ready. If it depends on variables from earlier cells, run those cells first.
2. 2Interrupt a long-running taskUse Stop/Interrupt while a task is running. Wait for the kernel to return to an idle state before starting another run.
3. 3Restart when you need a fresh stateRestart the kernel to clear in-memory variables. Saved source and existing rendered outputs are retained. Reopen the app when you need changed Environment settings to take effect.
4. 4Run the notebook again from the topAfter a restart, recreate variables by running the notebook in order. A NameError often means an earlier defining cell has not run.

· Enlarge screenshot

1

See the control up close

PreviousNext

Close

1. Run the current cell — Run a cell when it is ready. If it depends on variables from earlier cells, run those cells first.

1

2. Interrupt a long-running task — Use Stop/Interrupt while a task is running. Wait for the kernel to return to an idle state before starting another run.

2

3. Restart when you need a fresh state — Restart the kernel to clear in-memory variables. Saved source and existing rendered outputs are retained. Reopen the app when you need changed Environment settings to take effect.

3

4. Run the notebook again from the top — After a restart, recreate variables by running the notebook in order. A NameError often means an earlier defining cell has not run.

4

Check the result

After a restart, recreate variables by running the notebook in order. A NameError often means an earlier defining cell has not run.

If it does not work

• For NameError, run the cell that defines the missing name.
• For FileNotFoundError, check the working folder and keep the data directory beside the notebook.
• For ModuleNotFoundError, check package availability; downloading a file does not install its Python package.

Next steps

• Set environment variables
• Read tables, plots and interactive results

Contact support