We rolled out a hotfix today specifically to address this issue:
Please let us know if this keeps happening.