There are three failover scenarios we need to verify:

• Service shutdown before sending usages

Risk: remittance entities will stay at status “In Progress”
Action: The daily clean up cronjob will reset these entities to status “Pending” to be processed in the next hourly tick by the hourly aggregation cron job.

• Service shutdown after sending usages
  

Risk: remittance entities will stay at status “In Progress”
Two scenarios:
Producers will handle the previously sent aggregations and the status will be updated to “failed” or “succeeded”
The daily clean up cronjob will reset these entities to status “Pending” to be re-processed. Possible overbilling customers.
Action: To avoid overbilling customers, SWATCH producers will ignore messages older than 1 day (checking the updated_at.

• Service shutdown after failing to send usages
  

Risk: remittance entities will stay at status “In Progress”
Action: The daily clean up cronjob will reset these entities to status “Pending” to be processed in the next tick