Known issues
On this page
These are the problems known in release 2026.11.3, from its release notes. Each says what to do, where there's something you can do. The latest release is 2026.11.4. If that isn't 2026.11.3, that release's notes have its own list.
Your server
Section titled "Your server"- Only x86_64 (amd64) servers. Moorhold servers need an x86_64 processor. ARM is for the Moorhold app for Mac only.
- A second admin for updates and Proposals. One admin is enough for the sample data, for more memory and for the mail password set in the portal. On a server with two or more admins, an update asked for on the Updates page still waits for another admin to approve it, and a Proposal is still approved by someone other than the person who made it.
- An approval while an update runs by hand. If an admin approves an update in the portal while
someone runs
sudo moorhold upgradeon the server, the approved update can wait until the next daily update check. Runningsudo moorhold upgrade --approvedinstalls it sooner. - More memory on a small server. On a full server with less than about 24 GB of memory (the 12 GB and 16 GB sizes included), or a core server with 8 GB, more memory for a tool is refused: the portal says the server hasn't room, because Moorhold keeps 4.5 GiB spare above its apps' limits.
- Many people behind one address. The server limits how often one address can load the first-run pages. If many people reach Moorhold from one address, or someone keeps mistyping a password, an open first-run page can still be refused and show a blank page. Wait a minute, then reload it.
- The audit page and one admin's request. The audit log stores "Asked for and approved by" and
the admin's name for a sample data or memory request, but the portal's audit page doesn't show
those words. On the page, an ask for the sample data is a
setup.sample-askrow, and the server's work on it is two rows namedrequests.add-sample-data, one when it starts and one when it's done, with nothing on the page to tell them apart. - robots.txt comes out as one line. The portal and published tools serve robots.txt as a
single line,
User-agent: *\nDisallow: /\n, with each\nsent as the two characters, soDisallow: /isn't on a line of its own. The X-Robots-Tag header that tells search engines not to index them is right. - A reboot after a rollback to 2026.10.7 or earlier. Those releases can't stop Moorhold at shutdown, so a reboot shows services failing and restarting until Moorhold has started. They recover by themselves.
- Airflow's Triggerer shows as unhealthy. Moorhold doesn't run one, because nothing in Moorhold uses deferrable tasks. Moorhold's own health check ignores it.
- The words reconciler and reconciled. The pass summary after "Update the tools now", such as "3 resources reconciled", its refusals, a Waiting reason that ends "on the next reconcile", an agent's reply to a new proposal, the audit log and Moorhold's own logs use these words.
Data and the catalog
Section titled "Data and the catalog"- A source that runs the sample's own code. Removing the sample also removes its code, so while the sample is removed, a source that runs the sample's code is refused until the sample is added back. We've seen this only with a test source on our test server.
- The sample's metrics aren't saved or run. The sample data declares seven metrics, but its
marts list no readers and have no row-level rule, so Superset doesn't save them and no one can run
them through an agent. On a Stack of your own, Superset saves a mart's metrics once the mart lists
readers, under
readersor under its row-level rule. An agent can run them only on a mart with a row-level rule. - Metrics on the native Assets page. The page says it lists metrics, but none appears on it.
- Two lines on the native Assets page ask you to reload. Where the catalog is still being built, or is empty, the page says to reload it to check again. It doesn't check by itself.
- Lineage on a Stack without DataHub. The portal reads lineage from DataHub, so on a Stack without DataHub no page shows lineage, and the portal's menu has no Lineage item. The lineage service stores Airflow's events, and no page shows them.
- Changing the catalog after install. You can't change the catalog after install. A Stack that still declares the DataHub component can't read the native catalog, and the render says so.
- System tables for agents. Agents that search through DataHub's own MCP server see the system tables, because DataHub applies its default view only on its own pages.
Sleeping tools
Section titled "Sleeping tools"Tools can sleep when idle if spec.public.sleepWhenIdle is set. Unset, every tool keeps running.
- More memory for a sleeping DataHub. If a request for more memory for DataHub's services comes due while DataHub sleeps, the resize can fail and put the old size back. If it does, open DataHub to wake it and ask again.
- The launchpad and a sleeping tool. The launchpad can't tell that a tool is asleep, so a sleeping tool's tile can show it as not answering. Opening it wakes it.
- An agent working alone. An agent's calls to DataHub's MCP server don't count as use, so DataHub can go to sleep while an agent is working with it. The agent's next call wakes it.
Signing in
Section titled "Signing in"- Signing back in to DataHub returns to its home page. After you sign out of DataHub and sign in again from the signed-out page, you land on DataHub's home page, not the page you left.
- Signing back in after Superset's sign-out. After you sign out of Superset and sign in again from the signed-out page, you land on the portal's Proposals page. Open Superset again from the launchpad.
- DataHub on a shared computer. If the last person to use the browser didn't sign out, DataHub can open as them, with their access, until its session runs out, even after you sign in to Moorhold as yourself. Sign out before someone else uses the browser.
- Users & Groups in DataHub. If your role can't manage users, DataHub's Users & Groups page shows "Failed to load users!". That's DataHub's message when your role can't see the list of users.
- Working only in Airflow or Superset. Time spent in Airflow or Superset alone doesn't keep your Moorhold session going. If you use only one of them until the session times out, you see the sign-in page.
- API tokens made in Airflow. They keep working after you sign out, until they expire or are deleted in Airflow.