In the shared execution log files I noticed the find expression of the element, which cannot be located on the page, uses TagIndex. This said, I suspect this could be leading to the differences between both browsers.
In order to check if this is indeed the case, I would recommend you to modify the find expression
of that element by removing the TagIndex - you could include TagName instead. Possibly the ID of the element might be sufficient to identify the element but this depends on the application structure. Once you change that, please execute the test and double check if this will work as expected.
If the issue still persists, you can turn on the annotations (please see point 5. in this article
) and execute the test against Edge again. With this, you will be able to see which is the target element highlighted for that step. Can you please also share that with us?
Additionally, please let me know if you can share a sample test with us and if the application can be reached outside your network. I ask this, because it will be easier for us if we can reproduce the issue on our end in order to see what might be going wrong.
Thank you for your cooperation in advance.