rudder-data-path-diagnostician-maintainer

Trace missing Rudder data by following the evidence chain from UI queries through API routes, service aggregation, and underlying source or derived records. This diagnostic process classifies the failure boundary and uses read-only verification to produce an evidence-backed root cause.

Rudder Calendar empty events or wrong dashboard counts stem from failure boundaries like wrong target, empty source, filter-window mismatch, derived-data generation gaps, or sync/import gaps. Diagnosing the active runtime and organization scope identifies the specific failure category.

Yes, Rudder data lineage diagnosis applies to dev environments, prod-local Desktop, worktree previews, and remote deployments. It verifies the correct active runtime and organization scope before inspecting sources or proposing fixes for empty dashboards or broken chat output.

Data lineage diagnosis for derived data traces the evidence chain from UI requests through API routes and service aggregation to source records. It explains how current rendering and derivation projections work when data is already correct, mapping the full lineage from UI query to state.

Find where Rudder UI data comes from by tracing the evidence chain from the UI request through APIs, services, and database or derived sources. This explanation mode maps the full lineage from UI query to route, service, derived projection, and state.