I also experienced this bug in testing.
#55s workaround worked for me.

Reply via email to