### Discussed in https://github.com/apache/airflow/discussions/24548

<div type='discussions-op-text'>

<sup>Originally posted by **don1uppa** June 16, 2022</sup>
### Apache Airflow version

2.2.5

### What happened

I have a dag that starts another dag with a conf.   
I am attempting to start the initiating dag a second time with different configuration parameters.   I it to start the other dag with the new parameters.

## What you think should happen instead

It should use the new conf when starting the called dag

### How to reproduce

See code in squsequent message

### Operating System

windows and ubuntu

### Versions of Apache Airflow Providers

N/A

### Deployment

Docker-Compose

### Deployment details

_No response_

### Anything else

**Work around for now is to delete the previous "child" dag runs.**

### 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)
</div>
"""Test TriggerDagRunOperator."""
        task = TriggerDagRunOperator(task_id="test_task", trigger_dag_id=TRIGGERED_DAG_ID, dag=self.dag)
        task.run(start_date=DEFAULT_DATE, end_date=DEFAULT_DATE, ignore_ti_state=True)
        with create_session() as session:
            dagrun = session.query(DagRun).filter(DagRun.dag_id == TRIGGERED_DAG_ID).one()
            assert dagrun.external_trigger
            assert dagrun.run_id == DagRun.generate_run_id(DagRunType.MANUAL, dagrun.execution_date)
            self.assert_extra_link(dagrun, task, session)
    def test_trigger_dagrun_custom_run_id(self):