Hi @Martin!
We are currently working on a fix for this. It’s a result of an additional aggregation made by Looker Studio: