just a quick update here: Santiago G. is working on fixing this, appreciate your patience
seems to be an issue with a downstream vendor that we're sorting out
hi there- i'm back from ooo and we'll dig into this more today, appreciate your patience!
in the meantime- is the bug still happening? or is it on-and-off?
