Hello.
After upgrading Devolutions RDM Client to latest version: 2025.1.24.0 (Windows). Our users are reporting errors woth Search functionality in RDM.
The object you are searching for shows up in the search results, but when we try and go to that entry we get an "Entry not found error".
Restarting RDM seems to resolve the issue for a short time before it suddenly stops working again. 

RDM-error-2.jpg
RDM-error-1.jpg
Recommended Answer
.29 is now available
Stéfane Lavergne
I can also add that this is a multi-vault search. The seach brings you to the correct Vault, but does not bring you to the entry itself (Ref error message).
Hello,
Thank you for reaching out regarding this issue.
I was able to reproduce the problem and will report it to the development team for resolution.
They will work on fixing it, and I will keep you updated as soon as a fix is released.
Best regards,
Jacob Lafrenière
Any update on this?
Hello,
This should be fixed starting with our next minor update, 2025.1.26.0. We're hoping to release it next week.
Regards,
Hubert Mireault
Hello!
We just updated to 2025.1.26.0 today, but search is still not working.
I see no meantion of it in the patch notes either, and update on this?
Hello Lars,
Thank you for the feedback, we'll have one of our devs look at this ASAP. We've made a lot of fixes in 2025.1.26.0 but it's possible we missed something for this scenario.
Regards,
Hubert Mireault
The issues have been resolved and will be available in v2025.1.28.
Sorry for the inconvenience.
Stéfane Lavergne
Ok, any ETA on 2025.1.28?
Possibly the middle of next week, if not early in the week of April 7th.
Stéfane Lavergne
.29 is now available
Stéfane Lavergne
Sorry to keep bumping this post, but we have discovered that the same bug still exists if you try to right click an active connection and press 'select in navigation pane'

This only applies cross-vaults as the act of right clicking the connection automatically marks the connection in the vault.
ac97614d-8b37-4338-bf99-54c74d35e2fb.png
a603125f-f7d4-4127-8c9b-c8702f056831.png
No problem at all, I will have a look. Thank you for notifying us of the issue.
Stéfane Lavergne
The fix made in v2025.1.33 is going through acceptance testing and validation and should be released within the next few days.
Best regards,
Stéfane Lavergne