# Can we avoid updates that force me to debug on the command line please?

**URL:** <https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995>\
**Category:** Product Support\
**Created:** [August 23, 2025, 10:14am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995 "2025-08-23T10:14:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Benjol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benjol/32/3907_2.png) [@Benjol](https://meta.discourse.org/u/Benjol)\
**Post date:** [August 24, 2025, 7:43am UTC](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995/3 "2025-08-24T07:43:25Z")

</div>

You’re right, of course.

It’s just that I wasn’t expecting the first rebuild to fail, so that caught me off guard.  
The message _was_ there, but I because it was in the wall of log text, I lacked confidence that I would find whatever the problem was. For all I knew it was going to be some obscure exception buried in a call stack. Once AI told me, I saw it was right there near the bottom.

I guess this is what happens when one is a part-part time webmaster 😑

---

_[View the full topic](https://meta.discourse.org/t/can-we-avoid-updates-that-force-me-to-debug-on-the-command-line-please/379995)._
