Hey @John_Munson !
I think you’re right that this is the same issue reported here:
It looks like the team will work on this soon. Hopefully, we have it fixed for you soon!