In this short debugging session, we resolved a dbt data quality test blocker in the Quo (OpenPhone) messaging pipeline. A recent influx of orphaned message webhook events lacking an associated system phone ID was triggering relational constraint and non-null failures.
🚀 Key Accomplishments
1. Quo Message Event Cleaning & Pipeline Restoration
We diagnosed a test failure occurring during the automated build of stg_quo_messages.
The Bug: Raw incoming webhook events sometimes captured system-level notifications or administration messages that lacked a valid phoneNumberId.
The Fix: Added a strict non-null check in stg_quo_messages.sql:
where phone_number_id is not null
This filtered out orphaned communication records, restoring dbt pipeline health and allowing daily analytics to build successfully for production Looker reports.