As a workaround, adobe team disabled ntFileFolderElastic which was causing the issue in the desktop app and the errors in the logs.
And informed it as a bug and will be fixed in upcoming releases.
Adobe comment for reference:
The problem seems to be related to the use of the index ntFileFolderElastic with sort options that are not mapped in the index definition.
In this case, the index should not apply the sort clause that instead should be performed in OAK.
As a workaround, we have to disable ntFileFolderElastic on the affected environments.