Based on the knowledge sources, I can see that the "Failed to run dbt command" error is a common issue with Elementary Data's report generation. There are several potential causes and solutions: ## Possible Causes and Solutions 1. Version Compatibility Issues: Make sure your Elementary dbt package version is compatible with your edr CLI version. Since you upgraded to 0.18.0 (CLI) and 0.18.1 (package), there might be a mismatch. Try running:

dbt deps && dbt run --select elementary

This will rebuild the Elementary tables with the updated package version [Slack forum answer](https://slack.com/archives/C02CTC89LAX/p1741371617144259). 2. Memory Issues: The error

died with <Signals.SIGKILL: 9>

often indicates an out-of-memory issue. Since you're running in Cloud Run, you might need to increase the memory allocation for your container [Slack forum answer](https://slack.com/archives/C02CTC89LAX/p1711457384233159). 3. Missing Logs: To get more detailed error information, check these log files: -

edr_target/edr.log

-

/usr/local/lib/python3.X/site-packages/elementary/monitor/dbt_project/logs/dbt.log

You might need to modify your Docker container to preserve these logs for debugging [Slack forum answer](https://slack.com/archives/C02CTC89LAX/p1703686732161589). 4. Internal dbt Project Dependencies: Sometimes the internal dbt project in the edr CLI needs its dependencies updated:

cd /usr/local/lib/python3.X/site-packages/elementary/monitor/dbt_project    dbt deps

This has resolved similar issues for other users [Slack forum answer](https://slack.com/archives/C02CTC89LAX/p1674145950818659). If none of these solutions work, you might consider temporarily downgrading to a previous version that worked for you while investigating further, as one user mentioned doing in a similar situation [Slack forum answer](https://slack.com/archives/C02CTC89LAX/p1741371617144259). I hope this helps! Let me know if you need further assistance with any of these troubleshooting steps.