Thanks, @sheppard.austin, we're following this error in this other thread as well. We'll post an update as soon as we can