Hi James, I suspect it’s the following already reported (and apparently fix ready) bug:
Apologies if I’m mistaken.