This seems to be fixed now! Thank you for looking into this. Please resolve this conversation.
