main ← fix/rewind-initial-report-count
opened 01:07AM - 02 Jan 26 UTC
We changed rewind to fetch reports in batches, fetching only 3 to start with, an…d then fetching more as needed. However, we were actually fetching all reports server side then cutting down the results to only 3, which meant we were incurring unnecessary load on the server in the case where reports were not cached, leading to 502 errors in some cases.
This fix also necessitates changing the caching strategy. Previously, we would cache all of the reports at
once then when fetching an individual report we would pull from there. However now that we aren't fetching
all reports at once, we need to cache individual reports and fetch them if they are not cached.