# Troubleshooting terminated Pluto worker

**URL:** <https://discourse.julialang.org/t/troubleshooting-terminated-pluto-worker/86327>\
**Category:** Pluto\
**Created:** [August 25, 2022, 2:31pm UTC](https://discourse.julialang.org/t/troubleshooting-terminated-pluto-worker/86327 "2022-08-25T14:31:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![laggvar](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@laggvar](https://discourse.julialang.org/u/laggvar)\
**Post date:** [August 25, 2022, 2:31pm UTC](https://discourse.julialang.org/t/troubleshooting-terminated-pluto-worker/86327/1 "2022-08-25T14:31:47Z")

</div>

I have a notebook (cannot share, unfortunately) where the worker keeps terminating in the middle of an expensive computation. The REPL just tells me the worker terminated along with a `Unhandled Task ERROR` confirming the same.

I cannot reproduce the issue when including the notebook directly into the REPL, neither if Pluto is started with `Pluto.run(workspace_use_distributed = false)`. By print-debugging, it clear that the worker does not always terminate on the same line every time. I can also reduce the risk of termination significantly by adding `sleep(5)` in the i middle of the code.

Is there anything else I can do to debug this? Can I somehow get better information from the worker when it terminates?