Hey @bobwoodard
We have noticed this behavior, and have fixed this internally. Will be coming up in our future releases