Skip to main content

​
Reports: how to download

Use Download report to export the filtered history as a table (one row per call) for offline analysis in Excel or a BI tool. Reports are generated as CSV or XLSX files; the XLSX format also includes a summary sheet with totals, a breakdown by status and health, success rate, and average duration. A report always covers the same set of calls as the current history filters.

​
Report queue

Reports are generated in the background so large exports don’t block the page. The Reports button opens the panel of previously prepared reports:
  • a new report starts as pending, then processing, and finally done or failed;
  • reports don’t wait for analytics to finish — calls whose analytics aren’t ready yet are included with empty analytics columns;
  • the list shows the start time, finish time and duration of the build, so you can see whether a report is slow or the queue is stuck;
  • a report running longer than half an hour is marked taking longer than usual and keeps going;
  • at six hours the build is cancelled with the reason time exceeded: the queue slot is freed and the half-built file is not published. Such a report can be built again with a narrower period or fewer columns;
  • once a report is done, download it from the panel. You don’t have to wait with the panel open: when it is ready the dashboard shows a pop-up notification with the download link, and on failure one with the reason. The notification only lives in an open tab — close the dashboard and nothing arrives, though the report is still built;
  • download links expire after a retention period; an expired report shows as expired and must be generated again.

​
Which period is exported

A report inherits the period from the History filter, and the form itself has From and To fields so you can adjust it without leaving the dialog. That matters most on a campaign page: there is no History filter there, so the export period is set in the report dialog itself. When no period is set anywhere, the report takes the last 30 days. The form says so in a line, and the whole history toggle exports everything.
As soon as the period is edited in the form, or the 30-day default is in effect, the estimated row count stops being shown: it was computed for a different selection, and showing it on would be a lie.
Two heavy reports can occupy the queue. Reports are built in a shared pool: two unfiltered reports take both slots while a one-row report waits its turn. The time thresholds limit that situation without removing it — the most reliable way to get a file quickly is a narrower period and fewer columns.