Okay, fellow audit trailblazers, I need to pick your collective brains on a performance snag that's driving my team up the wall. We've been deep in our quarterly close cycle, and the final step—generating the master audit report PDF from AuditBoard—has suddenly turned into a marathon. We're talking 20, sometimes 30 minutes per attempt, and a few times it's just timed out entirely. This is a brutal bottleneck when you're trying to get final sign-off.
For context, our report isn't *that* crazy, but it's not trivial either:
* About 45 pages in total, with a mix of standard sections, executive summaries, and detailed findings appendices.
* We use a custom template we built out last year (heavily branded, with specific header/footer logic).
* It includes maybe a dozen dynamic data visualizations (mostly bar/line charts from our control testing results).
* We're on the "Professional" plan, and our instance has data for about 3 years of audits.
Things I've already tried or ruled out on my own:
* **It's not our local internet speed.** I've run it from different networks, and colleagues in different locations experience the same delay.
* **Browser doesn't seem to be the primary factor.** Tried Chrome, Edge, and even Firefox—the queue time server-side appears to be the constant.
* **The "light" preview generates quickly.** It's the full, print-ready PDF that crawls.
* I've experimented with breaking the report into two smaller documents, and the smaller ones *do* generate faster (like 5-7 mins), which points to a volume/complexity issue.
My big curiosity is what, specifically, in the report composition triggers this kind of processing quicksand? Is it:
* The number of embedded charts? (Is there a "sweet spot" we've blown past?)
* The custom template logic itself? I love the flexibility, but I wonder if we've over-engineered it.
* Some underlying data query that's running each time for the dynamic elements?
* Or is this just a known platform limitation during peak usage times, and we need to schedule this for 2 AM?
I'm about to start a systematic experiment—rebuilding the report piece by piece to isolate the choke point—but I figured I'd ask here first to see if anyone has already done the forensic work. Any war stories, confirmed triggers, or even AuditBoard support snippets you've received on this would be gold.
What's the most complex report you generate regularly, and how long does it take? Have you found any specific features or design choices that are absolute PDF killers? 🔥
Try everything, keep what works.