Overview

In Khoros Aurora Community versions prior to 26.2, the Admin Analytics reports may fail to load, display a blank or white page, or return incomplete data when a date range longer than approximately 30 days is selected. Reports scoped to the last 7 or 30 days are typically unaffected.

Symptoms:

• Admin Analytics report pages load as a blank or white screen when a multi-month date range is selected
• Summary metric cards and the data table fail to populate; the page shows a spinner indefinitely
• The issue affects multiple report types, including Member, Forum Discussions, Forum Board, TKB Board, Category, and GroupHub reports
• Reports scoped to 30 days or fewer load correctly
• The problem is more pronounced on larger, higher-traffic communities

Note: This issue has been resolved in Khoros Aurora Community version 26.2. If you are experiencing this problem, please verify your community version or contact support for upgrade information. This issue does not involve any data loss — all analytics data remains intact.

Solution

Step 1: Verify Your Community Version

1. Check which version of Khoros Aurora your community is currently running
2. If you are on version 26.2 or later, the issue should already be resolved
3. If you are on an earlier version, proceed to the workaround steps below or contact support to schedule an upgrade

Step 2: Apply the Workaround (For Versions Prior to 26.2)

If you need to access multi-month analytics data before your instance is upgraded, the following workaround may help by allowing the backend query results to be cached:

Option A: Wait and Retry

1. Navigate to Admin → Analytics → Reports and select your desired report
2. Set the date range you need (e.g., the past 6 months)
3. If the page loads as blank, wait 3–5 minutes on that page without navigating away — the backend query may still be processing
4. Navigate back to the reports list
5. Return to the same report — the previously selected date filter should be preserved
6. If the page is still blank, repeat steps 3–5 one or more times

After one or more attempts, the report typically loads because query results are cached in Elasticsearch and can be returned within the available time window on a subsequent request.

Option B: Use a Shorter Date Range

1. Instead of selecting a multi-month range in one request, select a date range of 30 days or fewer
2. Note your data, then shift the window and repeat for adjacent periods as needed

This avoids the conditions that cause the timeout and will load reliably on all versions.

Step 3: Request a Community Upgrade (Permanent Fix)

1. If your community is not on automatic upgrades and you are experiencing this issue, request an upgrade to version 26.2 or later: How to Manage Instance Upgrade Settings with the AI assistant
2. Refer to the Khoros Community Release Notes for the latest version schedule and deployment dates
3. Once upgraded to version 26.2, analytics reports will load reliably for multi-month date ranges without requiring any workaround

Tip: After upgrading to version 26.2 or later, you may notice that the summary cards load first, followed by the data table a moment later. This is expected behavior — the fix intentionally loads the summary and table sequentially to ensure reliability on large date ranges.

Summary

Admin Analytics reports failing to load for date ranges beyond 30 days is a known issue in Khoros Aurora Community versions prior to 26.2. It does not affect the integrity of your analytics data. The permanent fix is to upgrade to version 26.2 or later, which resolves the underlying timeout and resource constraints in the analytics pipeline. Until the upgrade is complete, the wait-and-retry caching workaround or reducing the date range to 30-day windows can be used to access the required data.

FAQ

Q1: Is any of my analytics data lost or corrupted because of this issue?
A1: No. This issue only affects the ability to retrieve and display analytics data in the Admin panel. All underlying data remains intact and will be displayed correctly once the upgrade to version 26.2 is applied.

Q2: Which report types are affected?
A2: All Admin Analytics report types can be affected, including Member, Forum Discussions, Forum Board, TKB Board, Category, GroupHub, Ideas, Events, and Blog reports. The issue is most pronounced on reports with many metrics and on communities with large data volumes, and is only triggered when a date range longer than approximately 30 days is selected.

Q3: After upgrading to version 26.2, will reports load instantly for any date range?
A3: Reports will load reliably for multi-month date ranges after the upgrade. However, loading times for very large ranges (e.g., 6–12 months on high-traffic communities) will be longer than for shorter ranges, and you will notice the summary cards loading before the data table. This sequential loading behavior is intentional and is part of the fix.