Bugzilla

Because the DAG docs indicate this job's failure should be addressed urgently (since the upstream data has a very short expiration), :akomar reached out to me directly.

Preliminary investigation indicates that there is a dependency on `copy-deduplicate` for the scheduled query that runs 
https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/search_terms_derived/suggest_impression_sanitized_v2_external/query.sql#L40. That query is defined here: https://github.com/mozilla-services/cloudops-infra/blob/master/projects/merino/tf/modules/log-routing/main.tf#L304, running at 2AM UTC.

:jbuck is going to try to manually trigger the scheduled query so that :wil can re-run the Airflow DAG.

It's worth nothing that this is a `_v2` of a dataset for which a `_v3` exists, and the latter appears to not have a dependence on stable table data, so it's perhaps worth investigating whether the workflow and scheduled query can be deprecated in its entirely. Absent that, making sure the dependence is well understood and documented in the DAG docs might be a useful remediation for when we have copy-deduplicate issues.

Because the DAG docs indicate this job's failure should be addressed urgently (since the upstream data has a very short expiration), :akomar reached out to me directly.

Preliminary investigation indicates that there is a dependency on `copy-deduplicate` for the scheduled query that runs 
https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/search_terms_derived/suggest_impression_sanitized_v2_external/query.sql#L40. That query is defined here: https://github.com/mozilla-services/cloudops-infra/blob/master/projects/merino/tf/modules/log-routing/main.tf#L304, running at 2AM UTC. `copy-deduplicate` had some issues for today UTC's run and was delayed beyond that time.

:jbuck is going to try to manually trigger the scheduled query so that :wil can re-run the Airflow DAG.

It's worth nothing that this is a `_v2` of a dataset for which a `_v3` exists, and the latter appears to not have a dependence on stable table data, so it's perhaps worth investigating whether the workflow and scheduled query can be deprecated in its entirely. Absent that, making sure the dependence is well understood and documented in the DAG docs might be a useful remediation for when we have copy-deduplicate issues.