Metabase says a table that exists is inactive, altough it isn’t. This happens for queries that had already been saved.
If i start the same exact query from scratch it returns the expected results.
I am running self hosted version 0.56.13
Metabase says a table that exists is inactive, altough it isn’t. This happens for queries that had already been saved.
If i start the same exact query from scratch it returns the expected results.
I am running self hosted version 0.56.13
Check the Metabase log for when the table becomes inactive. See if there is a process changing the table during that time.
If there’s an automated process that regenerates the table, Metabase might notice during the time the old table is gone or inaccessible and mark it inactive. Usually if access is restored within 14 days it will reactivate the table, but if it comes back with a new schema, the old table will be considered deleted and questions that reference it will stop working.
The “_mbarchiv” in the table title makes me think Metabase thinks the table the question references is gone for good.