New block skipped during SNP ingestion

[CharlieC3]

Describe the bug
When streaming events from SNP, it seems a block was skipped which resulted in a stall in the API. I believe this was caused by the redis message ID incrementing during a time when it shouldn't have been.

The fix was to manually edit the redis message id in the API database and decrement it by 10000, allowing the API writer to make a second pass over the events stored in SNP.

Logs