# How best to debug a Pluto notebook?

**URL:** <https://discourse.julialang.org/t/how-best-to-debug-a-pluto-notebook/87643>\
**Category:** General Usage\
**Tags:** pluto\
**Created:** [September 22, 2022, 1:31pm UTC](https://discourse.julialang.org/t/how-best-to-debug-a-pluto-notebook/87643 "2022-09-22T13:31:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Xavier\_Gonzalez](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xavier_gonzalez/32/36033_2.png) [@Xavier\_Gonzalez](https://discourse.julialang.org/u/Xavier_Gonzalez)\
**Post date:** [September 22, 2022, 1:31pm UTC](https://discourse.julialang.org/t/how-best-to-debug-a-pluto-notebook/87643/1 "2022-09-22T13:31:46Z")

</div>

A lot of times when I write julia in a Pluto notebook, I run into the following problem.

Let’s say I’m trying to change the name of variable. When I first change it, everything breaks.

Because Pluto is reactive, I would expect that as I correct instances of the old name of the variable to the new name of the variable, that everything would get fixed.

Instead, what I am increasingly finding is that when Pluto encounters and error, it “gets stuck,” and even when I make changes that should fix the error and press run on those cells, basically nothing happens.

The solution I’ve found is to just kill that Pluto instance and start a new one, but I’ve got to think there’s a better way.

Has anyone had similar experiences / know what might be happening?