Hello David,
thank you for reporting this issue. This seems like bug on our side that we need to fix.