Technically speaking of course this is a warning due to an unhandled error, and not an error itself. 😉
Hello @janmiddelkoop, could you please confirm if you’re using the latest available version and whether you’ve cleared all caches?
If you’ve done all this and the error is still present, please send me a support request through this link mentioning our conversation, and I’ll be happy to help you troubleshoot further.
Hi, this was using the latest version. Caches were cleared after update. I don’t know what caused the warning to appear, I haven’t debugged it or tried to reproduce it.
If it happens again, or you can reproduce it, please let me know so we can investigate further.