Hey everyone,
This is related to a bug fix that was rolled out this morning that’s having some unexpected consequences. Our team is pushing a fix to the fix now, which should resolve this behavior in just a little bit. If you continue seeing this in about a half-hour, please file a bug report!