Ya know, I'm with Stephanie here... at some point in time the testers monitoring the automation need to act professionally and understand the technical aspects of their job.
Little anectdote:
We had a set of automation that, for part of it, would take about 2 hours to run with no on screen interaction. It was set to run overnight to be completed by morning. When we got in, we'd check an e-mail inbox set aside to receive notifications of completed test runs. We KNEW how long it was supposed to take to run a test project and, if it took longer than that, we would know there was a problem. so... if we knew when the project was kicked off, we could look at the clock and know "Hey, look... it still has 2 hours to go" and go away and wait the 2 hours. ONLY if it was taking longer than expected would ANYONE attempt to touch the box and "fix" it. And, if they "fixed" it when it didn't need fixed and the person who had been waiting 2 hours for their test to be completed now has to RESTART the test, the person "fixing" it got an earful...