When the

edr report

command hangs or fails at the step:

Running dbt command --log-format json run-operation elementary.log_macro_results ...

it is typically due to one of the following reasons, as evidenced by multiple user reports and support responses: ### 1. Query Timeout or Long-Running Query If you have a large number of tests or a lot of data, the underlying dbt operation can take too long and eventually time out. This is especially common with warehouses like Redshift or Snowflake when querying large tables or long time windows. The error may appear as a timeout or simply as a hang with no progress. Workarounds: - Reduce the data queried: Use the

--days-back

flag with a smaller value (e.g., 7 instead of 30) to limit the time window. If it works for a smaller window but not a larger one, this is a strong indicator of a timeout issue. - Reduce executions per test: Lower the

--executions-limit

(default is 720). Try a much smaller value (e.g., 10) and increase gradually if it works. - Increase warehouse timeout: For Redshift, you can increase the

connect_timeout

parameter in your

profiles.yml

to allow longer queries to complete. > "the issue is that the query for your test results is taking too long... one option is to increase the timeout in your

profiles.yml

, this can be done using the

connect_timeout

parameter. another option might be trying to reduce the amount of data being queried. you can do that by playing around with the

--executions-limit

flag..." [Slack thread: Timeout and executions-limit advice](https://slack.com/archives/C02CTC89LAX/p1691169511715969) ### 2. Incompatible or Incorrect dbt/Elementary Versions Version mismatches between the Elementary Python package, the dbt package, and dbt itself can cause the command to hang or fail. Sometimes, upgrading or downgrading to compatible versions resolves the issue. Workarounds: - Ensure that the versions of

elementary-data

, the Elementary dbt package, and

dbt

are compatible. Upgrade or downgrade as needed. - After updating, run

dbt deps

and

dbt run -s elementary

to ensure everything is in sync. > "there was an issue with their path related to packages.yml. I've tried to apply the learnings from both but may have missed something." [Slack thread: Version and path troubleshooting](https://slack.com/archives/C02CTC89LAX/p1722421736771429) ### 3. Database/Schema Misconfiguration If the Elementary schema or database is not correctly set up or referenced in your

profiles.yml

or

dbt_project.yml

, the command may hang or fail. Workarounds: - Double-check that the schema and database for Elementary are correctly configured in both

profiles.yml

and

dbt_project.yml

. - Make sure the schema exists and is populated after running

dbt run -s elementary

. > "added this in dbt_project.yml but in profiles i had not included _elementary and somehow my datasets reference was incorrect and its fixed" [Slack thread: Schema configuration fix](https://slack.com/archives/C02CTC89LAX/p1695913966874839) ### 4. Resource Constraints or Process Killed In some environments (e.g., Codespaces, Docker, CI), the process may be killed due to memory or CPU limits, resulting in a hang or abrupt termination. Workarounds: - Check for system resource limits and logs indicating the process was killed (e.g., SIGKILL or SIGTERM). - Try running the command on a more powerful machine or increase resource allocation. > "died with <Signals.SIGKILL: 9>." [Slack thread: Process killed](https://slack.com/archives/C02CTC89LAX/p1718699125596869) --- Summary of Steps to Try: 1. Lower

--days-back

and/or

--executions-limit

. 2. Increase

connect_timeout

in

profiles.yml

. 3. Ensure all package versions are compatible and up to date. 4. Double-check schema/database configuration. 5. Check for system resource issues if running in a constrained environment. If the issue persists, check the

edr.log

and

dbt.log

files for more detailed error messages, as these often contain the root cause of the problem. If you need more targeted help, sharing these logs with the Elementary support team is recommended, as they can provide more specific guidance based on your environment and error details.