We use for-each loops with dynamic variables across many of our jobs, so addressing this would be a significant effort. Since a new task_id is assigned for each for-each iteration, if one of the iterations fails it’s difficult to determine which iteration value caused the failure using the proposed method. Would it be possible to request a feature enhancement to expose for-each loop task values in the system.lakeflow.job_task_run_timeline table or via the Runs API?