This file contains information about a completed invocation of dbt, including timing and status info for each node (model, test, etc) that was executed. In aggregate, many
run_results.json can be combined to calculate average model runtime, test failure rates, the number of record changes captured by snapshots, etc.
Note that only executed nodes appear in the run results. If you have multiple run or test steps with different critiera, each will produce different run results.
dbt source freshness produces a different artifact,
sources.json, with similar attributes.
args: Dictionary of arguments passed to the CLI command or RPC method that produced this artifact. Most useful is
rpc_method. This dict excludes null values, and includes default values if they are not null.
elapsed_time: Total invocation time in seconds.
results: Array of node execution details.
unique_id: Unique node identifier, which map results to
nodesin the manifest
status: dbt's interpretation of runtime success, failure, or error
thread_id: Which thread executed this node? E.g.
execution_time: Total time spent executing this node
timing: Array that breaks down execution time into steps (often
message: How dbt will report this result on the CLI, based on information returned from the database
adapter_response: Dictionary of metadata returned from the database, which varies by adapter. For example, success
code, number of
bytes_processed, and so on. Not applicable for tests.
rows_affectedreturns the number of rows modified by the last statement executed. In cases where the query's row count can't be determined or isn't applicable (such as when creating a view), a standard value of
-1is returned for