@chronoss2008 We haven’t seen any other reports of this issue and we haven’t been able to reproduce it internally. If you are still experiencing the issue, could you please provide a full screenshot of the error and exactly what you are doing when it happens?