Lukas Steger
06/24/2025, 10:24 AMjob_run_results , but where in the UI or the alerts can I access these? (I’m using elementary OSS)kapa.ai
06/24/2025, 10:24 AMkapa.ai
06/24/2025, 10:24 AMdbt_invocations table, and you can also use the job_run_results view, which groups invocations by job. This allows you to query and analyze job-related information directly from your data warehouse. - Elementary UI: If the job info was collected successfully, you can filter the lineage by job and see the details in the node info within the UI. This provides context for each run and helps with triaging and resolving data issues. However, job details are not currently included in alerts or reports in Elementary OSS. Multiple community discussions and official responses confirm that while the data is available in the schema and UI, it is not surfaced in alert messages or reports at this time. This feature has been requested but is not yet implemented [[Collect jobs info from orchestrator](https://docs.elementary-data.com/oss/guides/collect-job-data)](https://docs.elementary-data.com/oss/guides/collect-job-data) [Slack discussion](https://slack.com/archives/C02CTC89LAX/p1700642681686599). Summary: - Job info: available in the UI (lineage node info) and in the database (dbt_invocations, job_run_results). - Not available in alerts or reports as of now.