Hi @knutsp,
Thank you for reporting this issue.
We’ve just released a new version that includes a fix to prevent invalid MySQL identifiers and resolve the bad SQL syntax.
Could you please let us know if the issue is now resolved on your end if you disable your custom snippet?
Thanks!
