....Preparing an object recognition hint....

You’re correct: the object is either there or not. But TestComplete is designed to be “helpful” — it tries extended search strategies and visual recognition when objects are missing, which introduces delays. These steps are focused on disabling or avoiding those fallback behaviors.

1. Set Operation‑Level Timeout
   Don’t change the global 10 s timeout. Instead, adjust the operation-specific timeout to something like 1s.
   👉 https://support.smartbear.com/testcomplete/docs/keyword-testing/dialogs/set-auto-wait-timeout.html
2. Disable Self‑Healing (if it’s turned on)
   While self-healing won’t stop recognition hints, it can add extra fallback work.
   👉 https://support.smartbear.com/testcomplete/docs/testing-with/running/self-healing-tests.html
3. Use If…Then with WaitAliasChild() instead of IfObject
   IfObject may trigger deep fallback and hint generation. Using WaitAliasChild() (with a short timeout) is more direct and efficient.
   

   if (Aliases.MyForm.WaitAliasChild("ComboBox1", 1000).Exists) {
    Aliases.MyForm.ComboBox1.ClickItem("Option A"); 
   }
   

   This checks only the immediate alias-child, limiting unnecessary search.
4. Disable Extended Find / Auto‑search Features in Name Mapping
   Prevent TestComplete from automatically expanding its search beyond the mapped path.
   • Go to Tools > Options > Engines > Name Mapping.
   • In the Name Mapping Options, uncheck “Use extended find when possible”.
   • Optionally disable “Map object names automatically” or other auto‑search behaviors.
     👉 https://support.smartbear.com/testcomplete/docs/reference/options/engines/name-mapping.html
5. Use WaitAliasChild() for Object Detection
   Rather than relying on full deep path resolution, dynamically wait for a child object via WaitAliasChild(), with a short timeout, which avoids deep fallback lookups.

🔹 Create a Minimal Project for Testing (Diagnostic Step)

To isolate the problem, try creating a new lightweight TestComplete project with:

• Only essential NameMapping entries
• A single test case using WaitAliasChild() logic

This helps determine whether your current mapping or project structure is contributing to the slowdown.

🤖 AI-assisted response
👍 Found it helpful? Click Like
✅ Issue resolved? Click Mark as Solution

Imagine this scenario - you have two name-mapped objects in TestComplete - Object1, which is currently visible in the Object Browser (i.e. present in memory), and Object2, which is not visible (i.e. not in memory at the moment).

When you run the check:

if (Object1.Exists)

TestComplete finds Object1 already in memory, so it can immediately access its properties (like .Exists, .Visible, etc.) and quickly return true.

However, for:

if (Object2.Exists)

Since Object2 is not currently in memory, TestComplete doesn't immediately know whether it exists or not. So it enters a waiting state - controlled by the Auto-wait timeout setting (default: 10 seconds under Tools > Options > Playback > Runtime). During this time, TestComplete repeatedly tries to find Object2 in the application.

This is the issue that you are facing. To resolve this issue use one of the https://support.smartbear.com/testcomplete/docs/app-objects/common-tasks/waiting-process-or-window-activation.html#WaitMethods methods. For example,

var obj = object.WaitAliasChild("Object2", 1000); // Wait up to 1 seconds
if (obj.Exists)
  ...

Thanks Hassan & rraghvani,

At higher levels in the hierarchy this works well, but as I get to the lower levels this still takes ages. Ill need to keep playing with it.