When we re-run failed digital_bookplate_979 dag runs (using the airflow UI by clearing the tasks), we need to somehow trigger the poll_for_digital_bookplate_979s_email dag with the dag run ID so that we get an email. The poll_for_digital_bookplate_979s_email dag is triggered with a configuration like:
Create a new re-run dag for dag runs in failed state for digital_bookplate_979. Schedule should be monthly and it triggers the polling dag with the list of dag run ID's.
When we re-run failed digital_bookplate_979 dag runs (using the airflow UI by clearing the tasks), we need to somehow trigger the poll_for_digital_bookplate_979s_email dag with the dag run ID so that we get an email. The poll_for_digital_bookplate_979s_email dag is triggered with a configuration like:
Here is a sample request for querying for failed digital_bookplate_979 dag runs:
It returns data like this:
In the normal workflow, the polling dag is triggered from the digital_bookplate_instances dag and from the upload form.