Reply to thread

This might be a bug that our deploy process is triggering, though this does happen to be the first I've heard of it and it's been used for announcements for a while.


Regardless, it may be something we need to investigate to ensure that we're using the canonical URL everywhere we need to. If not, that would probably be the cause. (If we are, then I don't know what would cause this.)


Back
Top Bottom