Hi @jimmyd, thank you for your report!
Would you be able to provide the full stack trace of this error?
I suspect this might be a regression from a previous fix we did following this community report. Edit: not the case