It's fixed, thanks for reporting the issue. I assume you didn't have trouble doing the quest when it starts normally?
