We are using Databricks Asset Bundles (DAB) to orchestrate multiple workflow jobs, each containing multiple tasks.
The execution schedules is managed on the job level, i.e., all tasks within a job start together.
We often face the issue of rescheduling, i.e., we want to move an existing task, which already has a history of task executions / job runs. To reschedule a task, we might move it from one job to another. By moving the task from one job to another, we loose the tasks execution history. This is a problem for us, as we would like to understand the history of job executions as part of our logging / traceability of what happened in the past.

The question is: How is the task execution history associated with the task? Which properties of the task should we keep constant to keep the history associated with the task? There are task IDs, I guess? How can we make use of them?

Cheers
Julian