Confusion about {{run_id}} and {{parent_run_id}} variables for Databricks jobs (Azure)

essentialDatabr
Databricks Partner

In Databricks jobs on Azure you can use the {{run_id}} and {{parent_run_id}}

variables for a specific run: https://docs.databricks.com/workflows/jobs/jobs.html

For Databricks jobs with only two or more tasks, then {{run_id}} seems to correspond to 

task_run_id and {{parent_run_id}} seems to correspond to the job_run_id.

For Databricks jobs with only one task, then 

{{parent_run_id}} seems to correspond to the task_run_id, but what does the 

{{run_id}} correspond to? Is that the job_run_id?