OS: Windows 10 Version: Launcher 0.0.6, OpenRCT2 v0.1.2-developer build Commit/Build: 2691 (Git Hash: 85c8948)
As I was checking why certain rides were not fixed I stumbled upon some mechanics that were assigned to attractions that had no path leading to them, so I decided to let those rides never be inspected and move the mechanics that had those attractions assigned in order to refresh their ride that they wanted to visit. Both mechanics searched for a new ride but ended up going to the ride that now had the never to inspect ticked.
I am uncertain if it is reproducible in RCT2, I have never gotten the issue there, so it is very unlickely that this could happen.
Steps to reproduce:
1. Play RCT1 scenario "Dragon's Cove" imported with the original RCT Deluxe edition
2. Hire mechanics
3. Set ride to never be inspected
4. Move mechanic to new location
Screenshots / Video: