Root cause summary

The duplicate_subs test case on table mysql.default.subscriptions was aborted due to an upstream pipeline issue. Although the airflow.ingest_subs_daily pipeline shows a 'Successful' status for its last run on 2026-04-20T03:00:00Z, this timestamp is significantly older than the incident trigger time of 2026-04-26T10:59:14.187000+00:00, indicating a potential data freshness problem or a failure in a more recent, untracked pipeline run. All related DQ tests also aborted, suggesting a systemic issue rather than a data-specific one.

Evidence chain

1. The duplicate_subs test on mysql.default.subscriptions aborted at 2026-04-26T10:59:17.331298Z.
2. Other data quality tests on related entities, such as dbt.default.default.stg_products.freshness_check_products and dbt.default.default.fct_revenue.freshness_check, also aborted around the same time.
3. The immediate upstream lineage for mysql.default.subscriptions is the airflow.ingest_subs_daily pipeline.
4. The airflow.ingest_subs_daily pipeline last ran successfully on 2026-04-20T03:00:00Z, which is nearly a week before the incident, indicating a potential data freshness issue or a failure in a subsequent pipeline run not captured in the latest status.
5. No past incidents were found for the table mysql.default.subscriptions.

Remediation steps

1. Investigate the execution logs for airflow.ingest_subs_daily pipeline for any runs between 2026-04-20T03:00:00Z and 2026-04-26T10:59:14.187000+00:00 to identify any failures or delays.
2. Verify the data freshness of mysql.default.subscriptions to ensure it's being updated as expected.
3. Restart the airflow.ingest_subs_daily pipeline to ensure a fresh data load and re-run the duplicate_subs test case.