Wait timeout and waitproperty not working as expected

The WaitTime is in milliseconds. If you want 30 seconds, then the last parameter should be 30000,

SomeObj.WaitProperty(“Visible”, true, 30000);

Play around with the following code, against the website.

function Test1()
{
    var page = NameMapping.Sys.Browser("chrome").Page("https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_style_visibility").Panel("container").Panel("iframecontainer").Panel("iframe").Panel("iframewrapper").Frame("iframeResult");
    var item = page.TextNode("myP");
    item.WaitProperty("Visible", false, 30000);
}

The function you have written, is based on the number of iterations, there's no delay of waiting. Which is similar to this,

function TestIt()
{
    var intSecondsWaited = 0;
    var intSecondsToDelay = 30;
    
    do
    {
        intSecondsWaited++;
        Log.Message(intSecondsWaited);
    }
    while (intSecondsWaited <= intSecondsToDelay);
}

I am facing the same issue. All Wait method are completely useless for me. 

As a workaround I use codes like this : 

here, I want to see an object to disappear. 

function waitSpinner(){
  page = getPage("webPage");
  var elementHTML = page.FindElement("//mat-progress-spinner[@role='progressbar']");
  let stopTime = GetTickCount() + 4000;
  while(elementHTML.VisibleOnScreen == true && GetTickCount() < stopTime){
    Delay(100);
    optimisation.refresh_object(page);
  }
}

I'm going to try my best to explain the following scenario - I'm using your code to search for SubmitX button on website https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select which does not exist.

I'm going to pass in the following values into the method, CheckForExists(page, 3),

function main()
{
    // URL https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select
    var page = Sys.Browser().Page("https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select").FindElement("#iframeResult");
    CheckForExists(page, 3);
}

function CheckForExists(objElement, intSecondsToDelay)
{
    let intTimeOut = Options.Run.Timeout;
    Log.Message("Check for exists " + Options.Run.Timeout);
    Options.Run.Timeout = 1000;
    let intSecondsWaited = 0;
    Log.Message("starting do loop");
    do
    {
        intSecondsWaited ++;
        Log.Message(Options.Run.Timeout);
        // Find SubmitX button, which does not exist
        if (objElement.FindElement("//input[@value='SubmitX']").Exists)
        {
            Log.Message("object exists");     
            break;
        }
        else
        {
            Log.Message("object does not exist");
        }
        Log.Message(intSecondsToDelay);
        Log.Message(intSecondsWaited);
    }
    while (intSecondsWaited < intSecondsToDelay);
}

and Options.Run.Timeout = 1000, which sets the following project value,

When I run the code, it's waited 1000ms for the object to become available, as shown in Error. Since we set parameter intSecondsToDelay = 3, we can say it waited for 3 seconds (I'll get back to this point)

Now, if I pass CheckForExists(page, 2) and Options.Run.Timeout = 30000. When I run the code, it's waited 30000ms for the object to become available, as shown in Error lines. Since we set parameter intSecondsToDelay = 2, we can say it waited for 2 seconds. However, we can clearly see that it hasn't waited for 2 seconds, it's done 2 iterations of the loop, waiting 30 seconds each. Therefore, the total time it took was about 1 minute to complete.

In your example, it seems like Options.Run.Timeout is not settings the value correctly; performing 15 iterations and waiting 30 seconds each time.

I think this behavior is normal. FindElement (and other Find method) already use the timeout option of the project when performing the search. 

When I want to override this timeout and doing the wait in my own way, I always surrounding my code with :

Options.Run.Timeout = 50;  //set to 50ms
//my_code_that_contains_any_Find_Method
Option.Run.Timeout = 4000; //revert to initial value, 4s.

The example I have provided for WaitProperty, works fine. If it waits until the WaitTime period, it usually indicates that the TestObj is null, can not be found or it does not have that specified property.

My guess is, it that it's a code related issue.