Sorry, this was the oddest error. It got triggered by a timed action being resolved, or rather a bug in that code. So it didn't show up in my testing because when I did the testing, the timer was still running.