Is there a reason why the dbt invocation isn't uploaded also on run start? It would be helpful to use the elementary table

dbt_invocations

in an operation manner by checking whether there is a run in progress for a given tag, but this information is only uploaded in

on_run_end.sql

. In theory we could manually trigger the run operation, but it would still look like the run had finished due to this config:

'run_completed_at': now_str,

.

Hey Sindre! dbt invocations only run on

on-run-end

to capture the complete information about the invocation, including its completion time and status. Interested in understanding your use case. When would you check runs in progress? 🙂

Hei Noya! Seen from an operational perspective where we might have multiple different triggers running, it might be useful for us to check whether there are any ongoing triggers currently running, and being able to know which tag was run. I think it would be beneficial to treat

dbt_invocations

as an SCD2 type table with rows for both start and completion. For simplicity, the elementary report queries could still only look at the completion log entries.

Interesting! Noted, we will think about this. If you're thinking about writing this on your end, we'll be happy to discuss a contribution