We have the fix for this in QA as of this morning.
We will try to get the fix in before next weekly reset