@bequeef1 this issue was fixed today. Yay!