Newly created table is disabled and cannot be used for Field Filter

Get Help
1

Description:

Hi, I’m having an issue where a new table I added becomes disabled in Metabase right after creation, and I’m unable to use it in a filed filter.

Screenshot from 2025-12-08 14-21-57
Screenshot from 2025-12-08 14-21-57368×325 10.6 KB

What I’ve tried:

  • Forced a schema sync.

  • Forced a database rescan.

  • Verified that the table and columns exist and are queryable from the database.

No solution provided in previous discussion.

Additional Info: {
  "browser-info": {
    "language": "en-US",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "metabase-info": {
    "databases": [
      "postgres",
      "h2",
      "clickhouse",
      "mysql"
    ],
    "run-mode": "prod",
    "plan-alias": "",
    "version": {
      "date": "2025-05-05",
      "tag": "v0.54.6.2",
      "hash": "749c50d"
    },
    "settings": {
      "report-timezone": "Asia/Jakarta"
    },
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "16.0"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.7.4"
      }
    }
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "21.0.7+6-LTS",
    "java.vendor": "Eclipse Adoptium",
    "java.vendor.url": "https://adoptium.net/",
    "java.version": "21.0.7",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "21.0.7+6-LTS",
    "os.name": "Linux",
    "os.version": "5.14.0-570.21.1.el9_6.x86_64",
    "user.language": "en",
    "user.timezone": "GMT"
  }
}
2

Make sure the Metabase database user has access to the table in Clickhouse. Use the GRANT command to grant access.

4

Hi, thanks for responding. I checked, and the Metabase user already has access to ClickHouse. The issue doesn’t happen on all tables, only on a few of them.

5

Are these tables special in some way? Are they anything but standard tables stored on-disk?

Is there anything in the Metabase log when you run the schema sync? Looking for exceptions when the disabled tables are accessed.

6

@thalibarrifqi Have you found a solution to this? I’m experiencing the same with a table, and I am not sure how to debug this. FWIW, I’m self-hosting.

See screenshot below, table aux__referrer_metadata. It is disabled and can’t really unhide it, as there is no icon next to it.

image
image768×216 11.4 KB

7

no, all tables are same, but some of them randomly disable

8

I stll have no solution atm :pensive_face:

9

Mmh. That’s very strange. I am not sure what this means, as there are very few indications from the admin.

I’ve found a workaround: using the Metabase API to programmatically update the table's visibility. I’ve used the PUT /api/table/{id} endpoint, using {visibility_type=None}.

In Python, something like (assuming table id 1):

import requests

requests.put("http://localhost:3000/api/table/1",
    headers={
      "Content-Type": "application/json"
    },
    json={
      "visibility_type": None,
    }
)