@jaredl we haven’t yet - we temporarily disabled it and have been waiting to deploy 2.4.0….this occurred right after we upgraded to 2.3.4