Open ahafele opened 4 months ago
Need to think more about emailing errors - when a dag fails? would we know if the "export" failed? And OCLC specific emails.
We will know when a DAG run has some failed transmission of files. https://github.com/sul-dlss/libsys-airflow/blob/c664ace3093ee165542a603bb989931989e070bd/libsys_airflow/dags/data_exports/pod_transmission.py#L55
The failed files would be gathered in the next scheduled DAG run. For the full dump, the failed files would be retried once: https://github.com/sul-dlss/libsys-airflow/blob/c664ace3093ee165542a603bb989931989e070bd/libsys_airflow/dags/data_exports/full_dump_transmission.py#L61-L68
Regarding emails when we send records, I know we did this previously but I rather see emails when the DAG fails and not everytime it runs.
When an export has been sent to a vendor an email should go out to folio-load-reports@lists.stanford.edu with: Subject/body:
"Vendor name: A data export has been sent to ..."
For example, orafin dags generate emails.
No report needed for FULL DUMP