You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "roykoand (via GitHub)" <gi...@apache.org> on 2026/02/18 13:48:58 UTC

[I] Dag Run ID and Triggering User Name are not recorded properly for a Backfill job [airflow]

roykoand opened a new issue, #62126:
URL: https://github.com/apache/airflow/issues/62126

   ### Apache Airflow version
   
   3.1.7
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When running a second or subsequent backfill job for the same DAG, the DAG Run ID and Triggering User Name for Dag Runs generated by backfill are recorded incorrectly.
   
   As shown in the screenshot below:
   
   <img width="910" height="323" alt="Image" src="https://github.com/user-attachments/assets/ec24d89a-8027-474a-95ae-6f892b5d5cde" />
   
   First backfill works correctly `backfill_...` Run ID and correct Triggering User Name but second time it creates Dag Run with `scheduled_...` Run ID and fails to record Triggering User Name.
   
   ### What you think should happen instead?
   
   All backfill jobs should consistently use the `backfill__...` Dag Run ID format and preserve the Triggering User Name, regardless of whether it's the first or subsequent backfill for the same logical date.
   
   ### How to reproduce
   
   1. Run a first backfill job - everything works fine
   2. Run a second or more backfill job. You will notice a Dag Run ID that does not start with `backfill_...` and Triggering User Name
   
   ### Operating System
   
   macOS, Sequoia 15.7.2
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Dag Run ID and Triggering User Name are not recorded properly for a Backfill job [airflow]

Posted by "abhijeets25012-tech (via GitHub)" <gi...@apache.org>.
abhijeets25012-tech commented on issue #62126:
URL: https://github.com/apache/airflow/issues/62126#issuecomment-3922066698

   i would like to take it


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Dag Run ID and Triggering User Name are not recorded properly for a Backfill job [airflow]

Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #62126:
URL: https://github.com/apache/airflow/issues/62126#issuecomment-3930842712

   We will not assign people any more - more info https://lists.apache.org/thread/slgcqs2csn1fngn65g5srrqn8xtsghn7


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Dag Run ID and Triggering User Name are not recorded properly for a Backfill job [airflow]

Posted by "shivaam (via GitHub)" <gi...@apache.org>.
shivaam commented on issue #62126:
URL: https://github.com/apache/airflow/issues/62126#issuecomment-4211621160

   Investigated this issue. The root cause is in `_handle_clear_run()` (backfill.py) — when reprocessing an existing DagRun, it updates `run_type`, `triggered_by`, and `backfill_id` but misses `triggering_user_name` (not even accepted as a parameter) and `run_id` (not regenerated).
   
   For the fix, I'd suggest addressing `triggering_user_name` (clear bug — audit data is lost) but **not** updating `run_id`. The `run_type` is already correctly set to `BACKFILL_JOB`, and no production code derives run type from the `run_id` string prefix — the mismatch is cosmetic. Updating `run_id` on a live DagRun is non-trivial due to FK constraints from `TaskInstance` and its dependents, and not worth the risk for a display inconsistency.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Dag Run ID and Triggering User Name are not recorded properly for a Backfill job [airflow]

Posted by "shivaam (via GitHub)" <gi...@apache.org>.
shivaam commented on issue #62126:
URL: https://github.com/apache/airflow/issues/62126#issuecomment-4211647900

   @oykoand what do you think?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org