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

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.

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"
  }
}

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

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.

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.