Cannot summarize an SQL question

Hello!
Not seeing what I'm missing here, so asking a question on what seems like a bug:

I have a SQL question that works as a pivot base. I'm trying to summarize it to use the new pivot visualisation introduced in v 0.38

But I cannot even summarise my question by 2 metrics, if I do this:

then click "visualise", the result I get is a view of my questions without any groupings (without any error message), and if I click the top right button "show editor" again, my groupings options have disappeared, as if I had never clicked "summarize" in the editor.

This is not happening if I query directly my table, then the summarizing works.
Any idea of what could be the cause here? Happy to provide additional details,

thanks for the help!

Hi @hawisizu
Please post "Diagnostic Info" from Admin > Troubleshooting.
It sounds like you're seeing this issue:
https://github.com/metabase/metabase/issues/15725 - upvote by clicking :+1: on the first post

Thanks for the quick anser. Diagnostic info:
{
"browser-info": {
"language": "en-GB",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.11+9",
"java.vendor": "AdoptOpenJDK",
"java.vendor.url": "https://adoptopenjdk.net/",
"java.version": "11.0.11",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.11+9",
"os.name": "Linux",
"os.version": "4.9.0-11-amd64",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"postgres"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "11.7"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.2.18"
}
},
"run-mode": "prod",
"version": {
"date": "2021-04-27",
"tag": "v0.39.1",
"branch": "release-x.39.x",
"hash": "6beba48"
},
"settings": {
"report-timezone": null
}
}
}

Indeed it seems to be the same issue you mentionned