Understanding Report Jobs and Status
Why every report is tracked as a job, and what to check if a job shows failed.
Why "jobs" exist
Every report you generate, even a fast one, is tracked as a report job with its own record, this gives you a consistent way to see what's been generated and by whom, not just the immediate download.
Status meanings
A job typically moves through a straightforward lifecycle, queued briefly, then processing, then either completed (with a download available) or failed. Since Members reports currently generate synchronously, you'll usually see completed appear almost immediately.
If a report job shows failed, the most common cause is an overly broad filter combination that matched zero records, double-check your filters before assuming something is broken.
Where to find past jobs
Report history isn't currently a dedicated searchable archive, treat each generation as a fresh, standalone job rather than expecting to browse a long report history list.
Related Articles
Generating a Members Report
Step through the wizard to produce a PDF or Excel report of your membership.
Exporting Reports to PDF or Excel
When to choose PDF versus Excel, and what stays the same between the two.
Best Practices for Filtering Before You Generate a Report
Get your filters right the first time, since a synchronous report waits for the full generation to complete.
Common Mistakes When Building a Members Report
A short list of avoidable errors that lead to a report you'll need to regenerate.