shivaam commented on issue #59043:
URL: https://github.com/apache/airflow/issues/59043#issuecomment-4211206258
I've opened a PR to fix this: #64939
**Root cause:** When a backfill reprocesses an existing DAG run,
`_handle_clear_run()` updates `backfill_id`, `run_type`, and `triggered_by` but
never updates `conf` — so the old params persist.
**The fix:** Pass the user-provided conf through to the reprocess path and
apply it to the DagRun. When no conf is provided, the existing conf is
preserved.
Also added conf validation against the DAG's param schema so invalid params
are rejected upfront, matching what already happens for manually triggered runs.
**Follow-up items noted in the PR:**
1. `ValueError` from conf validation isn't caught by the backfill API route
(surfaces as 500 instead of 400) — pre-existing pattern, same gap exists for
manual triggers
2. The backfill UI form pre-fills DAG defaults, which could accidentally
overwrite custom conf on existing runs — a follow-up UI checkbox ("Override
parameters on existing runs") would address this
@potiuk would appreciate your review when you get a chance.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
