=== Report 1: 2025 Monthly Sync-Webhook Stuck Rate for the 4 Highest-Impact Tenants (written by Omar) === Engineer's note: Month is printed as the first calendar day of that month (date type) since TO_CHAR isn't available in this engine; sync-webhook matching uses ILIKE '%ERP%sync%'/'%WMS%sync%'/'%ACCOUNTING%sync%' on webhooks.name to catch close name variants, consistent with the prior sync-webhook report's approach. REPORT: 2025 Monthly Sync-Webhook Stuck Rate for the 4 Highest-Impact Tenants QUESTION: For the 4 tenants that account for ~91% of all stuck sync-webhook deliveries (Brennquell Kaffee, Cragsley Outfitters, Ampfeld Elektronik, Marrowby & Vane), has their stuck rate been stable all year or is it new/worsening? tenant_name | month | total_sync_deliveries | pending_or_retrying_rate_pct --------------------+------------+-----------------------+----------------------------- Ampfeld Elektronik | 2025-01-01 | 185 | 11.35 Ampfeld Elektronik | 2025-02-01 | 97 | 11.34 Ampfeld Elektronik | 2025-03-01 | 60 | 3.33 Ampfeld Elektronik | 2025-04-01 | 80 | 10.0 Ampfeld Elektronik | 2025-05-01 | 106 | 11.32 Ampfeld Elektronik | 2025-06-01 | 87 | 4.6 Ampfeld Elektronik | 2025-07-01 | 98 | 10.2 Ampfeld Elektronik | 2025-08-01 | 78 | 7.69 Ampfeld Elektronik | 2025-09-01 | 117 | 17.09 Ampfeld Elektronik | 2025-10-01 | 106 | 7.55 Ampfeld Elektronik | 2025-11-01 | 235 | 11.06 Ampfeld Elektronik | 2025-12-01 | 334 | 9.88 Brennquell Kaffee | 2025-01-01 | 1309 | 11.69 Brennquell Kaffee | 2025-02-01 | 1086 | 10.41 Brennquell Kaffee | 2025-03-01 | 1275 | 13.73 Brennquell Kaffee | 2025-04-01 | 1139 | 11.41 Brennquell Kaffee | 2025-05-01 | 1104 | 12.5 Brennquell Kaffee | 2025-06-01 | 1032 | 10.27 Brennquell Kaffee | 2025-07-01 | 1090 | 10.64 Brennquell Kaffee | 2025-08-01 | 1068 | 9.93 Brennquell Kaffee | 2025-09-01 | 1139 | 10.97 Brennquell Kaffee | 2025-10-01 | 1175 | 9.7 Brennquell Kaffee | 2025-11-01 | 1186 | 11.72 Brennquell Kaffee | 2025-12-01 | 1546 | 10.22 Cragsley Outfitters | 2025-01-01 | 1177 | 3.91 Cragsley Outfitters | 2025-02-01 | 705 | 5.11 Cragsley Outfitters | 2025-03-01 | 858 | 4.78 Cragsley Outfitters | 2025-04-01 | 900 | 4.56 Cragsley Outfitters | 2025-05-01 | 1045 | 5.17 Cragsley Outfitters | 2025-06-01 | 942 | 4.14 Cragsley Outfitters | 2025-07-01 | 1088 | 5.06 Cragsley Outfitters | 2025-08-01 | 816 | 4.9 Cragsley Outfitters | 2025-09-01 | 999 | 4.8 Cragsley Outfitters | 2025-10-01 | 1171 | 5.12 Cragsley Outfitters | 2025-11-01 | 1861 | 6.5 Cragsley Outfitters | 2025-12-01 | 2542 | 4.68 Marrowby & Vane | 2025-01-01 | 708 | 1.27 Marrowby & Vane | 2025-02-01 | 362 | 0.83 Marrowby & Vane | 2025-03-01 | 433 | 0.23 Marrowby & Vane | 2025-04-01 | 389 | 1.29 Marrowby & Vane | 2025-05-01 | 430 | 0.93 Marrowby & Vane | 2025-06-01 | 396 | 2.02 Marrowby & Vane | 2025-07-01 | 450 | 0.89 Marrowby & Vane | 2025-08-01 | 386 | 1.3 Marrowby & Vane | 2025-09-01 | 468 | 0.21 Marrowby & Vane | 2025-10-01 | 507 | 1.58 Marrowby & Vane | 2025-11-01 | 823 | 4.37 Marrowby & Vane | 2025-12-01 | 1073 | 0.37 (48 rows) === Report 2: Internal Health Check Signal Around the Nov 28 2025 Storefront API Outage (written by Ines) === Engineer's note: system_health_checks is not tenant-scoped in this report (it tracks internal platform components, not merchant data), so results are aggregated across all tenants per hour/component as requested. REPORT: Internal Health Check Signal Around the Nov 28 2025 Storefront API Outage QUESTION: Did our internal health checks detect a problem around the two carts.remind failure windows (2025-11-28, roughly 14:40 and 15:40 UTC)? hour | component | total_checks | unhealthy_checks | unhealthy_rate_pct | avg_latency_ms --------------------+----------------------+--------------+------------------+--------------------+--------------- 2025-11-28 12:00:00 | accounting_connector | 5 | 1 | 20.0 | 2085.0 2025-11-28 12:00:00 | checkout | 111 | 1 | 0.9 | 294.0 2025-11-28 12:00:00 | erp_connector | 54 | 2 | 3.7 | 466.0 2025-11-28 12:00:00 | marketplace_feed | 15 | 2 | 13.33 | 1422.0 2025-11-28 12:00:00 | storefront | 111 | 1 | 0.9 | 194.0 2025-11-28 12:00:00 | wms_connector | 13 | 0 | 0.0 | 99.0 2025-11-28 14:00:00 | accounting_connector | 5 | 0 | 0.0 | 96.0 2025-11-28 14:00:00 | checkout | 111 | 111 | 100.0 | 10000.0 2025-11-28 14:00:00 | erp_connector | 54 | 2 | 3.7 | 461.0 2025-11-28 14:00:00 | marketplace_feed | 15 | 0 | 0.0 | 101.0 2025-11-28 14:00:00 | storefront | 111 | 111 | 100.0 | 10000.0 2025-11-28 14:00:00 | wms_connector | 13 | 0 | 0.0 | 110.0 2025-11-28 16:00:00 | accounting_connector | 5 | 0 | 0.0 | 83.0 2025-11-28 16:00:00 | checkout | 111 | 3 | 2.7 | 451.0 2025-11-28 16:00:00 | erp_connector | 54 | 0 | 0.0 | 102.0 2025-11-28 16:00:00 | marketplace_feed | 15 | 1 | 6.67 | 730.0 2025-11-28 16:00:00 | storefront | 111 | 0 | 0.0 | 101.0 2025-11-28 16:00:00 | wms_connector | 13 | 0 | 0.0 | 119.0 (18 rows) === Report 3: Ticket Subject Lines from Affected Merchants Before the Nov 24 Failures (written by Bea) === Engineer's note: Query returns every matching ticket ordered by created_at (no row cap applied here); if the batch run returns more than 50 rows, only the first 50 will print per house rules and the analyst should check the total row count noted on the report. REPORT: Ticket Subject Lines from Affected Merchants Before the Nov 24 Failures QUESTION: In the weeks before the carts.remind failures showed up in our logs, did the 10 affected merchants' shoppers raise tickets that look related to carts, reminders, or duplicate/missing emails? tenant_name | created_at | subject | status | priority ------------+------------+---------+--------+--------- (0 rows)