It could have been a bug that was fixed in a previous update with a specific setting or use case you had on your page. I can't say for sure since I never fully debugged your page or saw the version you were using, but I'm glad you have it resolved now.