This was the same issue as the one on Oct 31. We finally managed to track the source of the delay, that being the incorrect reading of “high memory usage” in our queuing system that prevented more events from being added. We’ve added more memory to counteract this as well as increase the threshold to high memory usage. Furthermore, the internal alarm setup on Oct 31 helped catch this incident early & resolve it much faster than the incident on the 31st.