Match Rules Lost After period of time - RPA Solution
I have a created an un-attended RPA solution which is required to process around 50K cases from the platform within a windows application.
The solution is deployed across 10 desktops and works as expected, however after about an hour of processing the automation seems to lose focus on certain match rules which have previously worked in the automation.
**If I exit the runtime and restart the desktop this resolves the issue I am encountering however due to this being an un-attended solution this is not sustainable work-around.
Could anyone suggest why this is happening and provide a solution?
Since match rules don't change, I would assume that the issue is that your application is changing after N number of records. You can investigate the matching process in the logs when it first fails to see why the particular control you expect to match did not and see if the application did in-fact change something.
Another possible scenario is that previous records are not getting closed properly and your adapter is still matched to the prior controls and thus will not see the new ones. You could also confirm this in the logs by looking to see if the prior controls are getting destroyed when you close them.
A third possibility is that your application behaves differently when the screen is locked and after a period of time, the screen locks causing the application not to create controls that you expect to be created. I have seen many applications that know when the screen is locked and fail to create controls they would otherwise create when unlocked.