Running a report in Avero involves entering parameters and sending your request. Behind the scenes, our system is gathering the data you requested and it takes time to retrieve, compile, and display the data. Since this is all happening on our web-based platform, the communication to databases takes time and all internet traffic experiences some limitations on time; if a request takes too long, it may be rescinded; this is referred to as a "timeout".
To avoid experiencing timeouts, Avero has built-in capability to recognize the likelihood of a report taking too long to run as a result of the size of the data request and will continue processing your request outside of the web platform and email you the result when ready, usually in about 15 minutes but it can take up to 3 hours depending on the size of the request. When this happens, you'll see an alert like this:
What can I do to generate the report in Avero instead?
The reason we hit the limit is because of the size of the data request. There's no hard limit on the number of businesses or date range you can run a report for, but including many businesses, long time frames, or a more granular report increases the likelihood of encountering this error. To get around it, you can do one of the following:
- Reduce the date range
- Reduce the number of businesses included in the report
- Use a higher-level report
- For example, getting summarized data like a Group Sales Summary requires less data than item-level sales reports. Depending on your goal, you may be able to run a summarized report or use a summarized report as a filtering tool to focus your granular report
- Consider filtering out data you don't need (meal periods, businesses, order types, etc, that aren't relevant to your current need)