You've seen it happen. You ask your AMS for a report that crosses a few tables, pulls together billing data, subscription status, etc., and the screen just sits there. The spinner goes. And goes. And then you get the error.
Not an answer. An error. The system tried to give you what you asked for, grew impatient, and gave up.
Most platforms treat this as your problem. The query was too complex. The data set was too large. You should have narrowed your parameters, filtered more aggressively, and asked a smaller question. The error message is the system's way of saying that the question is too hard to answer in the time the browser allows.
We decided to fix that.
The Question Didn't Fail. The Interface Did.
When we were building the reporting engine inside Tangilla, we kept running into this exact scenario during testing. Some reports take time to process. They are the ones that join multiple data sources, span long date ranges, or touch every member record. They don’t take time because they're broken. They take time because they're hard.
So we built the Report Inbox.
For reports we know will take longer to process, we don't even attempt to render them in the interface. We send them straight to the background. The report engine does its work without a browser session holding its breath, without a countdown clock, without the threat of a timeout. When it's done, the report drops into your Report Inbox, and you get an email letting you know it's ready.
No error. No retry.
A Design Decision, Not a Workaround.
This matters more than it might seem at first glance. The choice to build a Report Inbox is a statement about what we believe association staff should be able to ask of their data.
Some questions are fast. "Show me this member's invoice history." That runs in a second and displays on the screen. Some questions are slow. "Show me every active member with an unpaid bill run invoice, across all associations, with subscription status." That question deserves an answer, too. It just needs a different delivery mechanism.
The Report Inbox lets both kinds of questions coexist. The fast ones render immediately. The complex ones process in the background and arrive when they're ready. Neither one gets punished for being what it is.
Only The Timetable Changes.
Once a report lands in the Report Inbox, you can download the results as a CSV, as an interactive HTML file you can share with anyone (even people who don't have a Tangilla login), or in some cases, as JSON for a vendor integration. The same output options you'd get from an instant report. The only difference is that you didn't have to stand there watching a spinner pretend to work.
We believe this is the right approach.
