Hi ankit001mittal,

How are you doing today?, As per my understanding, you're on the right path by using the system.lakeflow.job_task_run_timeline table to track job and task-level activity. While this table gives you rich info on task runs, it doesn't directly label whether a task is from DLT, regular jobs, or interactive sessions. However, you can usually identify DLT runs by checking the job_name or task_name fields—DLT pipelines often include the word "DLT" or the pipeline name itself, and the job_cluster_type may show DLT or PIPELINE in some cases. You can also cross-reference with the system.lakehouse.pipeline_events table (if available in your workspace), which contains DLT-specific activity. For interactive sessions (like notebooks), they typically won’t show up as scheduled tasks unless launched through jobs—so their cost tracking may need to be done via system.billing.usage or workspace-level cost reports. So yes, while it's not a direct flag, you can filter and classify based on naming patterns and job types. Let me know if you'd like help writing a sample query to separate them out!

Regards,

Brahma