Hi @sylvia.astrida,
It was an issue with Chrome 137, we have already fixed this issue in the latest 10.2.2 release. If you’re using an older version of KS, you can refer to this workaround.
Hope that this would help 
2 Likes