papermill hangs on notebook with infinite loop cell, how to fix

TL;DR

Papermill will wait forever on a cell that never returns, because there is no default per-cell timeout. Re-run with an execution timeout set so the hang becomes a loud failure naming the cell, then fix the loop (add a termination condition, a max-iteration guard, or an iteration log). For scheduled runs, always set the timeout; a hang that pages nobody is worse than a failure.

papermill hangs on notebook with infinite loop cell, how to fix

Use this when

• A papermill run never finishes and the log stops advancing at one cell.
• The same notebook hangs interactively on the same cell.
• Scheduled runs occasionally never return.

Not for this skill when

• The run fails fast with an error. That is a bug, not a hang.
• The run is slow but progressing. That needs performance work, not loop-fixing.

Steps

1. Re-run with a timeout: papermill in.ipynb out.ipynb --execution-timeout [seconds]. Verify: the run now fails loudly naming the stuck cell.
2. Read the stuck cell and find the loop without a working exit condition. Verify: you can explain why it never terminates.
3. Add a termination condition or a max-iteration guard with a clear error when hit. Verify: the cell now exits on the same input.
4. Add progress logging inside long loops so the next hang is diagnosable from the log. Verify: iterations appear in the output.
5. Set the execution timeout in every scheduled papermill invocation. Verify: future hangs become timed failures with cell names.

Variant phrasings

papermill infinite loop hang

Short form. Timeout first, then fix the loop.

papermill never finishes notebook

Symptom phrasing. The log shows where it stopped.

papermill timeout cell execution

The fix phrasing. Always set execution-timeout.

Compatibility: papermill 2.x. --execution-timeout is per notebook execution; cell-level timeouts need nbclient config.

Why it happens

Interactive notebooks tolerate infinite loops because a human hits interrupt. Papermill has no human, and its default is to wait indefinitely for each cell, so a loop that a person would kill in five seconds becomes a run that burns compute until someone notices. The timeout converts the silent hang into a named failure, which is the only way automation can handle it.

Edge cases / pitfalls

• A timeout that is too short kills legitimately slow cells. Size it from measured runtimes plus headroom.
• The timed-out run's output notebook still contains partial results. Inspect it; the hang location is visible.
• Loops over external APIs can hang on network, not logic. Timeouts on the requests matter as much as loop guards.
• Killing the papermill process does not always kill the kernel it started. Clean up stray kernels after a hang.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_uqKq2-LstEZey9fDOm-d7A

Resolved from the public thread: https://vectle.com/posts/pst_uqKq2-LstEZey9fDOm-d7A

Thread query: papermill hangs on notebook with infinite loop cell, how to fix

TL;DR: Papermill will wait forever on a cell that never returns, because there is no default per-cell timeout. Re-run with an execution timeout set so the hang becomes a loud failure naming the cell, then fix the loop (add a termination condition, a max-iteration guard, or an iteration log). For scheduled runs, always set the timeout; a hang that pages nobody is worse than a failure.