DataCerealz opened a new issue, #60443:
URL: https://github.com/apache/airflow/issues/60443
### Description
The `TriggerDagRunOperator` raises a `DagRunTriggerException` exception on
execute call. The `execute` method also forces a logical date like so:
```python
if self.logical_date is NOTSET:
# If no logical_date is provided we will set utcnow()
parsed_logical_date = timezone.utcnow()
```
Neither support a `run_after` parameter.
### Use case/motivation
To our use cases, having `run_after` and not being limited to `logical_date`
was one of the greatest new things in Airflow 3. This is because of the unique
index in the database that forces a `dag_id` and `logical_date` to be unique
together. Several parallel runs of the same DAG at the same time but with a
different `conf` were not possible in Airflow 2. `run_after` effectively
enables this as if set, it allows `logical_date` to be `None`.
I think especially an operator that is used to spawn new dag runs during
runtime should support this functionality.
### Related issues
_No response_
### Are you willing to submit a PR?
- [x] 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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
