Org Web Adapter

Editing hungryroot/jira/be_7859_exp_242_investigate_and_backfill_missing_favorites_experiment_data.org

:PROPERTIES:
:ID:       7fcd79fa-1b2f-4d43-91f8-e94ea8527de8
:END:
#+title: BE-7859 Exp 242 Investigate and backfill missing Favorites experiment data

- source :: https://hungryroot.atlassian.net/browse/BE-7859
- tags   :: [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]]
- epic   :: [[id:968d929c-769b-491b-8279-062193e001b6][EP-650 Exp 242: Favorites + User Cookbooks]]
- sprint :: [[id:b56af951-eac1-49af-9bea-101efe645abc][HR BE Sprint 111]]
- status :: [[id:ec92a960-cac1-4b05-b4f5-25a2935eea75][Status - To Do]]
- priority :: [[id:d81320f2-7767-4307-81ca-1dea4f3a434f][Priority - Medium]]
- points ::

* Summary

Fanny provided CSV files showing customer data missing from Exp 242 Favorites reporting. Suspected cause: data exists in prod MySQL but did not make it to the data lake/warehouse.

* Investigation steps

1. Check if ~CustomerTag~ rows exist in MySQL for affected customers:
   #+begin_src sql
   SELECT * FROM customer_tag WHERE customer_id = <id>;
   #+end_src
2. *Row exists → ETL problem.* Pipeline feeding ~shared_model.dim_customer_tags~ missed it (replication lag, filter bug, failed job). Escalate to data eng.
3. *Row missing → app never wrote it.* Trace why ~update_customer_tags~ (~app/services/api/tag.py~) was not called for that customer. May require a backfill.

* References

- Slack thread :: https://hungryroot.slack.com/archives/C0B7CUKNZ6F/p1780531230664279
- Source of truth :: ~app/models/customer_tag.py~ → DB table ~customer_tag~
- ETL chain :: Django app writes → ~customer_tag~ (MySQL) → ETL/dbt → ~shared_model.dim_customer_tags~