Thanks, I was able to reproduce this issue. This has been fixed for the next beta.