Hi @quantumodo,
Thank you for bringing this issue to our attention. We have successfully reproduced the bug at step 53 and agree that it is indeed a bug. We will address it in the next version.
Thank you for your patience!
