Use the same philosophy you use to find bugs in your application. ie, A good tester is curious of what's going on and dig deep until find the real culprit like a detective.
one things to investigate is timing TC is faster than most application so when TC is looking for object it may have not created,
sometimes it is there.
to guide you to right direction we need more information.
I have added delays in spots that is required. But I'm trying to explain to you, that there was nothing different. The only thing is really different is, I am opening test complete on a different day. I complete these tests, then save them. Re-open them another day to make sure they are still working and turns out some don't. The things it stopped at during a test, is as simple as clicking a program buttons then mousing over the menu to select a option. Like a drop down menu. I honestly, not even sure how can I "dig deeper". Its legit, it was working, and now its not. Is there some kind of logging or something I can provide you?
