I've located the source of the bug and fixed it. Will be doing a redeploy once some other issues are sorted.
Awesome, thanks
Can you confirm that the new version fixed the issue?
