Relation 'app' does not exist after failed migration to docker on Heroku

After a failed attempt to migrate from Heroku buildpack to docker deploy on Heroku,
all my metabase record are broken. I get an "relation 'app' does not exist at position ..." error.
My databases are correctly connected.
It seems thats the failed update messed up the configuration of Metabase internally

Any idea fixing this problem ?
I'll paste after the diagnostic 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/ Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.19+7",
    "java.vendor": "Oracle Corporation",
    "java.vendor.url": "",
    "java.version": "11.0.19",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.19+7",
    "": "Linux",
    "os.version": "4.4.0-1104-aws",
    "user.language": "en",
    "user.timezone": "Etc/UTC"
  "metabase-info": {
    "databases": [
    "hosting-env": "heroku",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "13.11 (Ubuntu 13.11-1.pgdg20.04+1)"
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.5.0"
    "run-mode": "prod",
    "version": {
      "date": "2023-02-19",
      "tag": "v0.45.3",
      "branch": "release-x.45.x",
      "hash": "070f57b"
    "settings": {
      "report-timezone": null

did you move to a newer version or to the max minor version of your major version? start by restoring a backup and sending us the logs if possible

I moved to latest version.

Restoring a database backup did the trick thanks @Luiggi !
The update had probably alter metabase database.

It is unclear to me what is the best option now to update to the lastest version of Metabase ( considering the latest blog article asking to update immediatly ) considering I am using heroku buildpack ...

which version did you move to?

I moved to V0.46.6.1

Update to the latest minor version (with patch) of 45. Then try to sort out the migration to 46

1 Like