Hey there @tokyoscarab, does this correlate with the following bug possibly?
(there’s a workaround for now as well in there)