This is to inform you that this is a known issue in version 14.1 66.55, and the engineering team is actively working on a fix.
At this time, we do not have an ETA for when the fixed version will be available. Once we receive any updates regarding the release or workaround, we will share the details with you.