App crashes when query result map has no :block/uuid (renderer error)

Search first

• I searched and no similar issues were found

What Happened?

Running an advanced query (via /Advanced query) whose result contains an entity map without :block/uuid crashes the app. The renderer throws a severe error and the app needs a restart.

Console log:

2026-09-18T09:21:58.293Z [severe] [frontend.worker.db-worker-node] {:db-worker-node-invoke-failed {:status 500, :code :exception, :error #error {:message "Renderer query result map has no UUID", :data {:value {:block/journal-day 20260805, :block/title "Wed, 05.08.2026"}}}, :message "Renderer query result map has no UUID", :method :thread-api/get-render-snapshots}, :line 326}

The crash happens in my main graph (migrated from file-based version). The exact same query did not crash in a small playground graph.

Query:

{:query [:find (pull ?h [*]) (pull ?p [:block/title :block/journal-day])
         :where
         (task ?h #{"Doing"})
         [?h :block/page ?p]]}

Reproduce the Bug

1. Open a DB-version graph with at least one task with status "Doing" on a journal page.
2. Insert an advanced query via /Advanced query:

   {:query [:find (pull ?h [*]) (pull ?p [:block/title :block/journal-day])
            :where
            (task ?h #{"Doing"})
            [?h :block/page ?p]]}

3. The app crashes with the console error Renderer query result map has no UUID (method :thread-api/get-render-snapshots).
4. Adding :block/uuid to the pull pattern avoids the crash.

Expected Behavior

The renderer should not crash when a query result map lacks :block/uuid. It should either render the result gracefully or show a query error, as in the file-based version where arbitrary pull patterns are supported.

Screenshots

No response

Files

No response

Browser, Desktop or Mobile Platform Information

• Linux Desktop 2.0.1-alpha+nightly.20260917

Additional Context

• Crash is reproducible every time in the main graph.
• The same query did not crash in a small, fresh playground graph on the same installation.
• Workaround: include :block/uuid in every pull pattern of the query result.

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

Start by reproducing the query from /Advanced query and trace the renderer failure at :thread-api/get-render-snapshots, using the console error as the entry point. Compare the DB-version behavior with the file-based version described in the issue; done means the result no longer crashes and is rendered gracefully or reported as a query error.