# SQL cells hidden not executed

**URL:** <https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853>\
**Category:** Feedback\
**Created:** [September 15, 2026, 11:08am UTC](https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853 "2026-09-15T11:08:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\
**Post date:** [September 15, 2026, 11:08am UTC](https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853/1 "2026-09-15T11:08:39Z")

</div>

SQL cells are not executed when the cell is hidden. Is this intended behavior?  
See : [https://observablehq.com/@neocarto/sql-cells-hidden](https://observablehq.com/@neocarto/sql-cells-hidden)

---

<div class="post-metadata">

**Author:** ![mbostock](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mbostock/32/9_2.png) [@mbostock](https://talk.observablehq.com/u/mbostock)\
**Post date:** [September 15, 2026, 1:22pm UTC](https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853/2 "2026-09-15T13:22:02Z")

</div>

That looks like a bug. I’ll investigate!

---

<div class="post-metadata">

**Author:** ![mbostock](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mbostock/32/9_2.png) [@mbostock](https://talk.observablehq.com/u/mbostock)\
**Post date:** [September 15, 2026, 5:10pm UTC](https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853/3 "2026-09-15T17:10:49Z")

</div>

Fixed! Sorry for the regression and thank you for the report.

---

<div class="post-metadata">

**Author:** ![neocarto](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/neocarto/32/6554_2.png) [@neocarto](https://talk.observablehq.com/u/neocarto)\
**Post date:** [September 16, 2026, 6:16am UTC](https://talk.observablehq.com/t/sql-cells-hidden-not-executed/10853/4 "2026-09-16T06:16:37Z")

</div>

Thank you for your prompt response and for resolving the issue.