@kapa.ai we started getting {} as values for dbt_run_results in execute and compile timestamp columns?

The knowledge sources do not explicitly mention

{}

(empty dict/object) as the specific value appearing in

execute_started_at

,

execute_completed_at

,

compile_started_at

, and

compile_completed_at

columns in

dbt_run_results

. However, there are a few related known issues that may be relevant to your situation: Known Related Issues 1. Null values in timestamp columns (dbt 1.8.x + Elementary ≤ 0.15.x) After upgrading to dbt 1.8.x, these timestamp columns were reported as

NULL

due to a bug in the Elementary package. This was fixed in Elementary 0.16.0. [GitHub issue] [Slack thread] 2. Nanosecond precision timestamps on BigQuery (dbt-bigquery ≥ 1.11 / dbt-fusion) Starting with

dbt-bigquery >= 1.11

, timestamps with 9-digit fractional seconds (nanoseconds) appear in these columns, causing

CAST(... AS TIMESTAMP)

failures on BigQuery. A workaround is to add this macro to your project: [BigQuery timestamp fix]

{% macro bigquery__edr_cast_as_timestamp(column) %}
    cast(
        regexp_replace({{ column }}, r'(\.\d{6})\d+', '\\1')
        as timestamp
    )
{% endmacro %}

Recommendations 1. Share more context — your Elementary version, dbt version, and data warehouse type would help narrow down the cause. 2. Upgrade Elementary to the latest version, as many timestamp-related bugs have been fixed in recent releases. 3. If you're on BigQuery, the

{}

values may be related to how the adapter response or timestamp strings are being parsed — the nanosecond precision issue is a known culprit there. The knowledge sources don't contain a specific documented case of

{}

appearing as a value in these columns, so I'd recommend opening an issue on the Elementary GitHub or reaching out in the Elementary Slack community with your version details and a sample of the problematic rows. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai on dbt fusion stable fusion - we recently upgraded to 0.25.1

I'm sorry, but the knowledge sources do not contain specific information about Elementary 0.25.1 with dbt-fusion stable and the

{}

values appearing in the `execute`/`compile` timestamp columns of

dbt_run_results

. The knowledge sources do cover related issues with dbt-fusion (e.g., source freshness compatibility, nanosecond timestamp precision on BigQuery), but nothing that specifically documents

{}

as a value in those columns after upgrading to 0.25.1. What I'd suggest 1. Check the Elementary changelog/release notes for 0.25.1 to see if there are any known breaking changes related to dbt-fusion stable compatibility. 2. Open a GitHub issue at elementary-data/elementary with: ◦ Elementary version:

0.25.1

◦ dbt-fusion version (stable) ◦ Data warehouse type ◦ A sample of the

{}

values and which columns are affected 1. Reach out in the Elementary Slack community — the team is active there and this type of dbt-fusion compatibility issue has been tracked and responded to quickly in the past. [Slack thread] The knowledge sources simply don't have enough detail about this specific version combination to give you a confident answer. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.