Hmm, the error is thrown by a plug-in I use so I'm not 100% sure there's a super easy way to get around it unless you go back to before you triggered the quest.
