Debugging these issues without seeing them is challenging. Problems running on different machines could be:
- Performance differences with the environments
- Different display settings. You said scaling it the same, what about screen resolution? Objects existing but not being visible can be an indication they are off screen. Does the automation set the window size for the application under test? We set it at the beginning of the run so we know it's always the same.
- Different settings in Tools > Options
- Name Mapping properties for objects that are sensitive to the environment. If they are using XY coordinates you're setup for failure.
For the issues finding the ("RescheduleDialog"), does the dialog appear when you run the test on your machine? I would use breakpoints and step through so you can see what's happening.