CU report interactivity spikes, reduce timeout / CU consumption

[Eric7]

We have embedded Power BI reports (application owns data) that sometimes cause a spike in the interactive (red) CU consumption, as seen in the screendump below. We are running capacity F32. The spike below lasted for 225 seconds and then failed. It consumed a lot of CU seconds during that period. Is it possible to set up somewhere that such spikes should timeout earlier than 225 seconds, thus consuming less overage?

[lbendlin]

If this is important to you please consider voting for an existing idea or raising a new one at https://ideas.fabric.microsoft.com/?forum=2d80fd4a-16cb-4189-896b-e0dac5e08b41