@KumarK6558 To me this seems like an issue where you might be attached to older versions of the controls. Basically, you are seeing a control that is no longer present as matched. This can happen in cases where the page is dynamically loaded and controls are added/removed/refreshed without refreshing the page. As a test, I would perform the following;

1. Create an automation to write a log message for the created/Destroyed events for all the relevant controls and their parents up to the page level, so you can easily see when controls are being created and destroyed. This is actually already logged by the adapter, but I have found that for a lot of people they prefer to explicitly write their own log messages so they can see exactly what they are coming from. If you do write to the log, make sure to preface the messages with some common string so you can easily locate them.
2. Before you execute your automation steps, call the Rematch method on your page being sure to set the Detach parameter to true so it destroys all of the children and re-matches them.
3. If this works, then I would not use the Rematch as the solution immediately. I would investigate the matching to see if perhaps there is some difference in the initial controls versus the ones you are trying to operate on.
4. If you do need to rematch, I would do so at the control level on as few as possible.

If anything, a thorough examination of the logs will be required to determine exactly what is happening.