We’ve just deployed a hotfix for this issue.
Please note that the fix will not apply to any instance that was already started.
We’re aware of and working on this bug.
We don’t yet have an ETA for a fix, and will provide a further update when we do.
Thank you!