The reason the

query_id

column in the

dbt_run_results

table is always empty when using Redshift is that, as of the information available, only certain dbt adapters (like Snowflake and, more recently, Databricks) return the

query_id

as part of their response. Redshift does not currently provide the

query_id

in the adapter response, so Elementary cannot populate this field in the

dbt_run_results

table for Redshift users. This is confirmed by support staff who noted that "only Snowflake returns the query ID as part of its response" and that for other warehouses, the field remains empty unless the adapter is updated to include it. There is no indication in the knowledge sources that Redshift currently supports this feature or that a workaround exists within Elementary for Redshift at this time [Slack thread](https://slack.com/archives/C02CTC89LAX/p1675682994311369). If Redshift adds support for returning the

query_id

in the future, and the dbt adapter is updated accordingly, Elementary will be able to capture and store it automatically, as it does for other platforms once the adapter supports it.