Metabase error column field.special type does not exist

some of the questions that were working fine earlier have suddenly stopped working and we are getting the following error :"column field.special type does not exist". please let me know what needs to be done to resolve this.

  "browser-info": {
    "language": "en-GB",
    "platform": "Linux x86_64",
    "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.7+10",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "",
    "java.version": "11.0.7",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.7+10",
    "": "Linux",
    "os.version": "4.15.0-1058-aws",
    "user.language": "en",
    "user.timezone": "UTC"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "11.12"
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.2.8"
    "run-mode": "prod",
    "version": {
      "date": "2020-05-28",
      "tag": "v0.35.4",
      "branch": "release-0.35.x",
      "hash": "b3080fa"
    "settings": {
      "report-timezone": null

Hi @nivedita1
That is because you have upgraded to a newer release and the downgraded again.
Metabase does not support downgrading, you'll have to revert to your backup.
Latest release is 0.41.2:

we have 2 metabase instances connecting to the same postgresql set up db...both these instances are of different versions.. cld this b the issue?

@nivedita1 That is absolutely not supported and you will end up with corruption.

If you are running multi-instances to the same application database, then the instances should always be running the same version.

got it...thanks..

will upgrading the lower metabase version fix this issue?

@nivedita1 No, you have to revert to your backup or upgrade all instance to the same newer version.

will upgrade the lower version to the same version as the other and check..