A small result can still require a large search. When a filter matches only
a small part of your organization’s history, WeGive may need to check many
records to find those matches—or confirm that there aren’t any. Choosing a
relevant date range can help focus the search, especially for organizations
with a large amount of historical data.
Why fewer results can take more time
Suppose your organization has several years of payment history. Opening a list
of recent payments may let WeGive find enough records to fill the first page
quickly. Filtering for a payment type or status that appears only occasionally
may require searching much farther back to find the matching records.
The same applies when no records match. Depending on the filters, WeGive may
need to check the full history included in your search before it can confirm
an empty result.
Loading time depends on how much information must be checked to find your
results. The number of rows displayed on the page is only part of that picture.
Why different filters can load at different speeds
Advanced filters let you ask specific questions about your data. Some can find
matches directly; others need to check more records or information connected to
them, such as giving history or group membership. Combining several conditions
can require additional checks, even when the final list is short.
This means two searches in the same table can take different amounts of time.
A filter that loads quickly for one organization may take longer for another
with more history or fewer matching records.
Focus the search on the period you need
When your question relates to a particular period, choose a date range that
covers it. For example, to review payments that succeeded last month, filter
by Succeeded At for that month. See
Getting a Report of Last Month’s Successful Payments.
Choose the date field that matches your question. A payment’s creation date
and the date it succeeded can be different. A narrower range also excludes
records outside that period, so keep the full history when you need it—for
example, when checking for older payments that still need attention.
A relevant date range can help reduce the work involved. It does not guarantee
the same loading time for every combination of filters.
If the table does not finish loading
If a table repeatedly fails to load, shows an error, or is unusually slow even
for a focused date range, contact WeGive Support. Share the table name, filters,
date field and range, and approximately when you tried the search. These details
help us investigate the specific view you’re using.