Yes. Our rolling back to ring-core 1.14.2 corrected the issue for us, but before we update to 1.15 and beyond, we need to fix whatever is gumming up the works in our code.