You click a report in Altru and nothing happens. Or the spinner runs for two minutes and then you get a blank frame, a generic error, or a timeout. The rest of Altru seems fine: you can look up constituents, ring up a sale, open a membership. Only reports are broken.
That pattern is common, and it usually comes down to one of three things: a problem on Blackbaud’s side, a problem in your browser, or a report that is asking for more data than it can return in time. The trick is figuring out which one you have before you spend an hour clearing caches for an outage you can’t fix.
First, decide whether it’s you or everyone
Altru is hosted by Blackbaud, and reports are generally rendered by a reporting service that sits alongside the main application. That is why reports can fail while daily sales, constituent records, and queries keep working. When reports go down for everyone, nothing you change locally will help.
Three quick checks answer the “is it me?” question:
- Check Blackbaud’s system status page. Blackbaud publishes service status and incident notices for its hosted products. If Altru reporting shows a degraded or investigating status, you have your answer. Subscribe to notifications there so the next one reaches you before staff start filing complaints.
- Ask a coworker to run the same report. Same report, same parameters, different computer. If it fails for them too, it’s not your browser.
- Try a small, simple report. Pick something with a narrow date range that normally loads in seconds. If that works but your usual report doesn’t, the problem is likely the report itself, not the service.
If the status page is clear and a small report also fails for several people, open a case with Blackbaud support. Status pages sometimes lag behind real problems, and your case may be one of the first reports of a new incident.
If it’s only you: browser causes
When one person can’t load reports and everyone else can, the browser is the usual suspect. Work through these in order, testing after each one:
- Pop-up blocker. Some reports and exports open in a new window or tab. If your browser silently blocks it, it looks like nothing happened. Allow pop-ups for your Altru site address.
- Private window. Open Altru in an incognito or private window and run the report there. If it works, a cached file or an extension in your normal profile is interfering.
- Extensions. Ad blockers, privacy tools, and some password managers can block embedded report frames. Disable them for the Altru site rather than uninstalling.
- Cache and cookies. Clear them for the Altru domain, close the browser fully, sign back in.
- Supported browser. Blackbaud lists supported browsers for Altru. If you are on something outside that list, or a version that is badly out of date, switch before troubleshooting further.
- Network. A workplace firewall or content filter can block the reporting service even when the main site loads. If reports work from home or a phone hotspot but not on the office network, bring in whoever manages your network.
If it’s one report: the report is too heavy
Reports that pull a full year of sales, every constituent in the database, or detailed transaction lines across all programs can run long enough to time out. They tend to fail at the worst times: month-end, year-end, right after a big event when the data volume jumps.
Things that usually help:
- Narrow the parameters. Run the year as four quarters, or one program at a time, then combine the results.
- Run it at a quieter hour. Early morning, before the sales day starts, often goes better than mid-afternoon.
- Use a query instead. If what you need is a list or a total rather than a formatted page, a query exported to a spreadsheet is often faster and more reliable than a report. Many admins keep a saved query version of their heaviest reports for exactly this reason.
- Check custom reports separately. If the failing report is a custom one someone built or had built for you, it may be the report’s design rather than Altru. Compare against a standard report covering similar data.
What to send Blackbaud support
A good case gets resolved faster. Include:
- The exact report name and the parameters you used.
- The time it failed (with your time zone) and any error text, word for word, or a screenshot.
- Whether other users see the same thing, and whether smaller reports work.
- Your browser and version, and what you’ve already tried from the list above.
That saves a round of “can you try clearing your cache?” and gets you to someone who can look at the service side.
Have a fallback for the reports you can’t miss
Reporting outages are usually short, but they have a way of landing on the morning someone needs a daily sales reconciliation or board numbers. A little preparation makes them a nuisance instead of a crisis:
- Identify the three or four reports your organization truly depends on, such as daily cash reconciliation, membership counts, and revenue by program.
- Build a query that returns the same core numbers for each, and test it once against the report so you trust it.
- Write down where those queries live and who can run them, so the person covering the desk on a Saturday isn’t stuck.
- For finance close, agree ahead of time that a query export is acceptable backup when the report won’t render.
Quick answers
Why do queries work when reports don’t?
Reports generally depend on a separate rendering service, so a problem there can break reports while the rest of Altru, including queries, keeps running.
Will rerunning the report over and over help?
Rarely. If it’s a heavy report timing out, repeated attempts can make things slower. Narrow the parameters or wait, then try once.
How do I know when an outage is fixed?
Watch Blackbaud’s status page or your open support case, then confirm by running a small report before trying the big one again.
