Describe the bug
Currently the report processor assumes that the non-total weekly cumulative measurements are the reach measurements. This causes the processor to fail when non-total weekly cumulative measurements do not have reach, or when they have other measurements such as frequency or impressions.
Steps to reproduce
Create a report_summary_v2 where one of the report_summary_set_results does not have reach, the processor crashes.
Component(s) affected
Report Processor
Version
v0.5.29