Hi all,
Thanks for sharing the details. We’ve been able to reproduce the issue in-house. While our team investigates and works on a fix, we recommend reverting to version 26.11.1 if this issue disrupts your workflow.
We’ll update this thread as soon as a fix is available.
Regards,
Srishti