This was a small regression that happened when we migrated to a more performant backend, the fix is already inbound and should be deployed later today!