File too large when running edr report, whats the fix?

There are several flags you can use to reduce the size of the

edr report

output file: 1. Reduce --days-back The most effective lever. Default is 7 days — try lowering it to 3 or even 1:

edr report --days-back 3

[Report size workaround] 2. Lower --executions-limit Controls how many historical test invocations are loaded per test. Default is 720 — reducing it significantly cuts memory and file size:

edr report --executions-limit 100

[executions-limit explained] 3. Disable passed test metrics Removes detail for anomaly detection tests that passed:

edr report --disable-passed-test-metrics true

4. Disable failed test samples Removes the row-level samples shown for failed tests:

edr report --disable-samples true

[All flags combined] 5. Combine all options for maximum reduction

edr report \
  --days-back 3 \
  --executions-limit 50 \
  --disable-passed-test-metrics true \
  --disable-samples true

[Combined approach] 6. Full-refresh Elementary tables (last resort) If the Elementary tables themselves have grown very large, a full-refresh reduces history (at the cost of losing old data):

dbt run --select elementary --full-refresh

[Full-refresh workaround] > Note: Reports can grow especially large if you have hourly anomaly tests with long training periods, many custom dbt tests, or a high volume of test results. If none of the above flags are sufficient long-term, Elementary's cloud solution handles large environments better than static reports. [Large env context] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.