Coming in October: Async Reporting for Apricot
⏱️ We’re changing how large Native Reports run in Apricot, so administrators and reporting users can get big reports and exports without hitting the two-minute browser timeout.
Many of you told us the same story. A large report spins, times out, and you narrow the date range, retry, or split it into smaller reports. Some of you also told us about export failures and runs that quietly stopped. We heard you, and we built a better way.
What’s changing 🔄
Administrators can now turn on background processing for individual Native Reports. When someone runs or exports one of those reports, Apricot processes it in the background. You can leave the page and keep working.
Who it affects 👥
Apricot administrators who set up Native Reports, and anyone who runs or exports them. It’s available on all instance types. Reports that an administrator doesn’t turn on keep running exactly as they do today.
What it means for you ✨
-
✅ Large reports and exports finish instead of timing out
-
📊 You can see each run’s status on the report page: queued, running, completed, or failed
-
🔔 You’re notified in the app when your report or export is ready, or if something goes wrong
-
🔒 Exports download through a secure link that only the requesting user and organization can use
Target timing 📅
We’re targeting October 2026. This may change, and we’ll update this post if it does.
Do you need to do anything? 🙋
No action is required. Background processing is off by default. If you have reports that often time out, an administrator can turn it on in Report Properties.
A few things to know 💡
-
Changing filters won’t run the report automatically. Click Refresh when you’re ready.
-
Exports are available for 48 hours, then they need to be re-run.
-
Background reports can’t be used in Bulletins. Check your Bulletins before turning this on for a report.
-
Print Mode for these reports needs a recent saved run.
Learn more 📚
💬 Which of your reports time out most often today, and how do you work around it?