This visual has exceeded the available resources.

The visual's query is too heavy for the query resource limits.

Why it happens

• High cardinality on the axis (e.g. raw URLs instead of page keys).
• Expensive measures — many nested CALCULATE calls or iterators.
• Too many data points, or a relationship fan-out inflating the scan.

How to fix it

1. Reduce points: Top N, filters, or a higher grain on the axis.
2. Simplify measures — use variables, avoid repeated context transition, pre-aggregate.
3. Lower cardinality by normalising keys; verify no relationship is fanning out.