AQUILA | Noise Corrector did not complete - flagging an 'INTERNAL_ERROR' in NC Logs

[abelmasry]

Context

• Google ran a report on December 4th, which was completed successfully.
• The Aquila Accounts Team ran a report on December 10th, and it was also completed.
• Alastair ran seven reports on December 12th, all of which were completed.

However, upon reviewing the noise corrector logs, we observed an 'INTERNAL_ERROR'. This indicates that the noise corrector did not execute as expected in the specified instances.

Steps to reproduce

1. Log into Aquila
2. Create Report
3. Select campaigns
4. Select reporting dates and demographics.
5. Select Cumulative Reach Data tick box
6. Select ‘Media Channel’ for ‘Measure Incremental Reach by’
7. Select any options
8. Submit report

Component(s) affected
Noise Corrector

Environment
Aquila PRD

[SanjayVas]

The steps to reproduce here refer to some system outside of Halo. This is the repository for Halo CMM, meaning issues must be filed with respect to the interactions with Halo software. Assume that Halo engineers have no knowledge of any non-Halo system, including UIs (e.g. I've never seen the Aquila UI and have no idea how it works, as it's not Halo code).

This means the steps to reproduce here would be something like "Call post_process_origin_report tool with a Report that X properties".

Furthermore, just mentioning a status code (INTERNAL_ERROR) does not give sufficient information to diagnose anything. We need more relevant details/logs.