hi,

try to add more time in Test Settings -> Run -> object synchronization timeout.

https://admhelp.microfocus.com/uft/en/23.4-24.2/UFT_Help/Content/User_Guide/Test_Settings_-_Run_Tab.htm?Highlight=Object%20synchronization%20timeout#mt-item-2

if the issue persists, please contact Support team for help.

James

Not quite what I was looking for.

That is already set at 20 sec and should be long enough.

It is not really the errors that are an issue, it is the time between steps that seems to need slowing down.

If ALM launched the tests in debug mode it would be slow enough (I think) to get a clean run.

It would have to be checked on a case by case basis as why UFT is finding the object too soon.

In general, putting a wait would not be ideal, a better way to do it is to check if there's any property that you can rely on to make sure the object is actually visible/enabled and use waitproperty to wait for it to reach that status, or rely on other objects which can indicate that the target object can be interacted with.

Yep - done that

As per my original description: I have input so many wait conditions, there is more of them, then there is actual testing code.

Guess you misread my reply, adding wait is NOT ideal, please check my other suggestion.

Sorry that my explanation is not clear - what I mean by wait conditions is: waiting for a condition to appear / visible, using loop so it only looks for the condition for 30 time / 30 secs, while the wait symbol exists on page do not continue, etc and yes, wait 1 or wait 2.

Sometimes there is actually nothing that changes on the page, or the page opens with 'No Orders Found' but that is not true because it is still searching and then it appears. I also use refresh on the page and then wait for the wait symbol to stop pulsing and then check etc etc.

But, I think we are getting off track

MY Question:

Anyone know a way to slow down the speed that scripts are being run when launched from ALM.

Sorry that my explanation is not clear - what I mean by wait conditions is: waiting for a condition to appear / visible, using loop so it only looks for the condition for 30 time / 30 secs, while the wait symbol exists on page do not continue, etc and yes, wait 1 or wait 2.

Sometimes there is actually nothing that changes on the page, or the page opens with 'No Orders Found' but that is not true because it is still searching and then it appears. I also use refresh on the page and then wait for the wait symbol to stop pulsing and then check etc etc.

But, I think we are getting off track

MY Question:

Anyone know a way to slow down the speed that scripts are being run when launched from ALM.