Hi everyone,I wanted to talk about an issue I created AIRFLOW-699, there's an
integrity constraint regarding the dag_id and the execution_date that makes it
impossible to trigger two times with different parameters a specific dag at the
same second.
As we are using airflow as the scheduler at the end of a complex notification
process, during high load scenario, these things happen.
Is there any hard reason for this uniqueness constraint ?
Regards,
Olivier Girardot

Reply via email to