If you're exporting the Forecasted vs. actual report and select all queues, you may see a generic error instead of your CSV. Here's why this happens and how to work around it.
Why does the export fail when I select all queues?
When you select all queues for a Forecasted vs. actual export, the request also pulls in data from any child queues. This can trigger a mismatch between forecasted and actual data on the backend, which causes the export to fail with a generic error message. This can happen even for a short date range, such as a single day.
Keep in mind: This is a known, currently unresolved limitation. We don't have a timeline for a fix yet, but we're tracking it internally.
How do I work around this?
Until this is resolved, export with fewer queues selected at a time:
- Open the Forecasted vs. actual report.
- Select Export.
- Choose a smaller group of queues instead of Select all.
- Select Export to download that CSV.
- Repeat for the remaining queues, then combine the CSV files if you need a single master file.
How do I know if this is the issue I'm running into?
You'll typically see a generic error when exporting Forecasted vs. actual with all queues selected, regardless of the date range you choose. If you get the same error with only a few queues selected, this is likely a different issue — contact us so we can look into it.
Questions? Contact support@assembled.com and we'll be glad to help.
Comments
0 comments
Article is closed for comments.