No, WaitChild and WaitAliasChild is limited to the single child tier. Same goes for all the WaitNNN methods. If you need to traverse multiple tiers and you don't know the structure - or it's unreliable - you will have to use Find methods (FindChild, FindChildEx, FindAll). The winner would be if you can reliably Map & Alias them, since it's faster, but sometimes Find methods are unavoidable. Find methods can also accept a timeout as parameter, so you can make this short as well. It will return early the moment it finds the object though, so you can afford to not make it TOO short and not allow TC to find it. The more specific you can be with your property values for your find, the better, so try and get those ientification details as specific as possible.
Seperate thought. You may just be going too fast for TC to keep up. That is where Wait is better than Find. You can however, in web applications, also be running into AJAX issues. TC caches the mappings, so when AJAX changes the web page, TC doesn't always know - it has the old page layout cached or doesn't know about the child yet. In this case, consider using Refreshmapping/RefreshMappingInfo() on the parent object before trying to find the child
