@SteveWatson - thanks for reporting, should be fixed now.