Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Admin |
The published limits that shape what you can build in Explore. Zendesk splits them into two kinds, and the distinction matters: a strict limit stops you, a recommended one degrades quietly.
Reports: the strict limits
| Rows | 50,000 |
| Loading timeout | 2 minutes |
| Explosions | 30 |
| Attributes within each drill level | 20 |
| Nested calculations | 3 levels |
| SQL query length | 1 million characters |
Reports: the recommended limits
| Metrics and attributes combined | 40 |
| Filters | 10 |
| Conditions per formula | 200 |
Columns a visualisation can carry vary by type: 100 for pie, funnel, bullet, gauge, picto, radar and parallel sets; 500 for table and word cloud; 1,000 for auto, treemap, relational, sunburst, sparkline and dot; 3,000 for area, column, line, KPI, bubble and waterfall.
Dashboards
| Live dashboards per account | 100 (strict) |
| Applied filters on a live dashboard | 5 attribute values per filter (strict) |
| Scheduled delivery attachment | 20 MB (strict) |
| Scheduled delivery timeout | 20 minutes (strict) |
| Dashboard restrictions | 10 on Professional, 500 on Enterprise (strict) |
| Tabs per dashboard | 10 (recommended) |
| Components per tab | 35 (recommended) |
Exports
An Excel export is limited to 50,000 rows and 16,000 columns. Combined with the 50,000-row report limit, that means a report you can see is a report you can export, and neither will tell you it stopped early.
The one that bites first
Rows per report. A report grouped by ticket, or by individual customer, reaches 50,000 quickly and truncates without a warning, which looks like a number that has stopped growing.
Group by something with fewer values, or filter harder.
Dashboard limits are a design hint
The recommended figures are generous: 35 components on a tab is far past the point where anybody reads it. Long before you reach a limit, a dashboard with twenty reports has stopped being read. Tabs help, and splitting into two dashboards for two audiences usually helps more.
Slow is a signal, not a limit
A report taking a long time is usually reading more than it needs: too wide a date range, no filters, grouped by something with thousands of values. Narrowing it is both faster and more readable, and it keeps you away from the 2-minute timeout.
Exports are not a data warehouse
Where somebody wants the full history in a spreadsheet every week, the answer is usually a proper export route or a scheduled dashboard, not repeatedly pushing against the export limit.
Check before you promise
If somebody asks for reporting over several years at ticket level, confirm the history and the row limit before committing. That conversation is much easier in advance.
Comments
0 comments
Article is closed for comments.