Overview of Queuing Reports
Reports can be manually or automatically queued to run at a later time.
Reports, whether opened individually or in dashboards, can take a long time to run if their database queries attempt to query a large amount of information. However, you can queue reports with intense queries so you can continue to work on the administration interface while the reports run in the background. When the queued reports have been run, you can open them and immediately view their data.
You can manually queue reports that you think may take a long while to run or that you want to view at a later time. If the application determines that a report will take an excessive amount of time to run, which can result in unnecessary load on your database, you’re given the option to queue the report using the report’s current search parameters. If you choose not to queue the report, you can select more restrictive search parameters for your report and try to run it again.
If your site is configured to use a report database (also referred to as a replication database) for reporting purposes, queuing works somewhat differently than it does on sites without a report database. See How Queuing Works on the Report Database.