Station message ID 86281 was created on July 2 but on the 14th was still being served even though it didn't exist in the table:
{"id":86281,"motd":false,"message":"Trains between Leicester and Kettering / Birmingham may be cancelled or delayed by up to 30 minutes. More information can be found in \u003ca href=\"https://twitter.com/hashtag/Leicester?f=tweets\"\u003eLatest Travel News\u003c/a\u003e.","station":["AUD","BDM","BEE","BHM","BWS","CBG","CEH","CHD","CLM","DBY","ELY","EMD","HKM","HNK","KET","LBO","LCN","LEI","LGE","LTN","LUT","MCH","MHR","MMO","MNE","NBR","NCT","NOT","NUN","OKM","PBO","SHF","SIL","SMD","SSD","STP","SWD","SWS","SYS","WEL","WLE"],"category":"Train","severity":1,"date":"2019-07-02T23:51:16.3185272+01:00","self":"https://d3.a.a51.li/message/86281"}
The issue looks like the cache retaining an entry after the on-disk copy was deleted.
Hopefully the version that's now live is not having this issue after I changed the algorithm used to expire cache entries. I've not heard of anything since the new back end went live a couple of weeks ago.
Station message ID 86281 was created on July 2 but on the 14th was still being served even though it didn't exist in the table:
The issue looks like the cache retaining an entry after the on-disk copy was deleted.
src: https://twitter.com/Shenandoah09/status/1150074484369633280