Thanks @clong trying that out, and we definitely saw that error from what that issue you pointed out. tracking it all down now