### 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>
provided_execution_date = event[1]["execution_dates"][0]
        try:
            dag_run = session.execute(
                select(DagRun).where(
                    DagRun.dag_id == self.trigger_dag_id, DagRun.execution_date == provided_execution_date
                )
            ).scalar_one()
        except NoResultFound:
            raise AirflowException(
                f"No DAG run found for DAG {self.trigger_dag_id} and execution date {self.execution_date}"
            )
        state = dag_run.state
        if state in self.failed_states:
            raise AirflowException(f"{self.trigger_dag_id} failed with failed state {state}")
        if state in self.allowed_states:
            self.log.info("%s finished with allowed state %s", self.trigger_dag_id, state)
            return
        raise AirflowException(
            f"{self.trigger_dag_id} return {state} which is not in {self.failed_states}"
            f" or {self.allowed_states}"
        )