The error message you’re seeing:

Failed to get Elementary dbt package version: {'returncode': 1, 'cmd': ['dbt', '--log-format', 'json', 'run-operation', 'get_elementary_dbt_pkg_version', '--project-dir', '/edr_stager_dbt_project'], ... "reason": "saved manifest not found. Starting full parse." ...

is a common one when running Elementary in GitHub Actions. Based on the knowledge sources, here are the most likely causes and troubleshooting steps: 1. Missing or Misconfigured dbt Profile - If the

elementary

profile is missing or not correctly set up in your

profiles.yml

, dbt will fail to run operations. Make sure your

profiles.yml

(or the secret/environment variable you use for it) contains a valid

elementary

profile with the correct target and credentials. This is a frequent cause of errors like

Could not find profile named 'elementary'

or failures during the

get_elementary_dbt_pkg_version

operation. Double-check that the profile is available to the GitHub Action at runtime and that the schema is set as expected for Elementary, not just for dbt itself, as the requirements may differ slightly between the two [[source]](https://slack.com/archives/C02CTC89LAX/p1710456181524819). 2. Missing dbt Packages or Artifacts - Elementary requires certain dbt packages to be installed for its commands to work. If you are ignoring the

packages.yml

file or not running

dbt deps

before the Elementary step, the required macros (including

get_elementary_dbt_pkg_version

) may not be available, leading to this error. Ensure that your workflow installs all necessary dbt packages before running Elementary [[source]](https://slack.com/archives/C02CTC89LAX/p1717056816868139). 3. Permissions to Write Packages - The action may need permission to write to the packages directory in order to install dependencies. If your workflow or environment restricts this, it can cause failures when Elementary tries to install or access required packages [[source]](https://slack.com/archives/C02CTC89LAX/p1717056816868139). 4. Manifest Not Found - The message

saved manifest not found. Starting full parse.

is informational and usually not the root cause of failure, but if the run fails immediately after, it may indicate a deeper issue with the dbt project setup or the environment in which the action is running. Recommended Steps: - Ensure your

profiles.yml

is present and correctly configured for the

elementary

profile. - Make sure you are not ignoring the

packages.yml

file and that you run

dbt deps

before the Elementary step. - Check that the GitHub Action has permissions to write to the packages directory. - If you are using environment variables or secrets for credentials, verify they are correctly set and accessible in the workflow. If you continue to see issues, please provide the full log output and your workflow configuration for more targeted troubleshooting. Let me know if you need help with a specific part of your setup!