...
We looked at a message found to have gone through that queue during the period the DataExportService was not the new Rabbit broker (a placement update, at 2:31 AM on 30/07/2021) and retrieved its trail through its correlationId: metabase link.
We checked whether that record had been exported by the DataExporter or not and it seems like it did, presumably proving data has been exported regardless of this issue (probably stored/pent up somewhere in the ESR interface and then finally flowing through once the DataExportService got put on the new Rabbit broker).
Timeline
: ??:?? - Other services migrated to new RabbitMQ broker
: 10:05 - Old RabbitMQ broker deleted from AWS by Liban
...
: 11:11 - Liban and Marcello start investigating to verify whether any data is missing
e.g. check DB for Applicants exported 27th-29th:
Placements should have a tick
Message in the audit database
Root Cause(s)
Deletion of the old RabbitMQ broker in AWS.
Dispersed/scattered configuration