This usually happens when the report is being filtered by a single (and wrong) invocation, even if you don’t explicitly pass

--select

. A few things to check/try based on the docs and Slack threads: 1. Use the correct syntax with

--select

The invocation filters must be passed via

--select

, not as a bare argument. For a specific invocation ID, run:

edr report --select invocation_id:XXXXXXXXXXXX

The docs only show this form, not

edr report invocation_id:...

. [Generate report] 2. Confirm the invocation_id actually exists in Elementary tables The CLI will only show data for invocations that Elementary has recorded in its own schemas. If the invocation is from before Elementary was installed or before it was correctly configured,

edr report

will return an empty report even if you have dbt artifacts elsewhere. [Historical runs; Invocation filter] Make sure the

invocation_id

you’re using comes from

elementary_test_results

in the Elementary schema you’re pointing

edr

at. 3. Try removing invocation filters and using a time window If you want to see all tests (including past ones) instead of a single invocation, generate the report with a days-back window:

edr report --days-back 30

This includes all invocations in the last 30 days, not just the last one. [Days-back usage] 4. Be aware of current limitation in the UI Even though

elementary_test_results

holds historical runs, the Test Results tab generally shows tests that are currently defined in

dbt_tests

(latest definitions). Historical failures for tests that no longer exist in your project won’t appear as “active” tests in the default report; you must filter by the specific invocation to see them. [dbt_tests vs history] If you are already using

edr report --select invocation_id:...

, the

invocation_id

definitely exists in

elementary_test_results

, and you still get 0 tests, the knowledge sources don’t provide a clear root cause. In that case, the next recommended step from support is to inspect and share

edr_target/edr.log

so the team can look for errors during report generation. [Empty report troubleshooting] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.

You’re right that

edr

is calling

elementary_cli.get_test_last_invocation

in the background:

... "macro_name": "elementary_cli.get_test_last_invocation", "macro_args": {"invocation_id": "ac4c97cc-740d-489e-a76b-6b674e1abcc2"}

This is expected behavior when you use `--select invocation_id:...`: the CLI passes your

invocation_id

into that macro to resolve the last test invocation associated with it. [EDR issue 1777] However, there is a known bug where

send-report --select invocation_id:...

doesn’t filter correctly and ends up mixing or ignoring invocations in the summary, even though the HTML itself is filtered. [Slack thread on send-report; GitHub issue 1777] The knowledge sources don’t explicitly say this same bug affects

edr report

, but your log line and “0 tests” behavior are consistent with the invocation‑filter logic not behaving as expected. From the docs, the intended usage is:

edr report --select invocation_id:ac4c97cc-740d-489e-a76b-6b674e1abcc2

and it should show only that invocation’s tests. [Generate report guide] Given that: 1. You have data in

elementary_test_results

/

test_result_rows

. 2.

edr

is clearly receiving your

invocation_id

. 3. The report still shows 0 tests. the most likely explanation (based on the available sources) is that you’re hitting the same or a closely related bug in the invocation‑filter path. Workarounds the docs/support suggest: • Use a time window instead of invocation filter, e.g.:

edr report --days-back 30

This bypasses the

get_test_last_invocation

path and should include all tests in that period. [Days‑back usage; Support suggestion] • Verify the

invocation_id

you’re using is exactly the one stored in

elementary_test_results

(same schema/DB that

edr

is configured to use). [Invocation filter usage; Slack answer] Beyond that, the knowledge sources don’t provide a concrete fix for this behavior in

edr report

. The recommended next step from support in similar cases is to share

edr_target/edr.log

and, if it looks like a bug, open or add details to an issue on GitHub (issue 1777 is already tracking a very similar problem for

send-report

). [Slack support guidance; GitHub issue 1777] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.