Hah! Not at all man, I think you had actually fixed it, and our queries internally just weren't anticipating things to work correctly. I think that table has been the bane of @fmanco for the past week or so 😉