Hey there!
I’m experiencing the same issue. The exact same error note occured after updating the plugin from v1.10.2 to v1.10.14.
I temporarily switched back to v1.10.2 now but I’d be grateful for any kind of advice on how to solve this issue @trsupsys.
Kind regards,
Caro
