@MichaelBishop This has been fixed in v1.0.0.50