• When an application group is created and application is published from the group, scope administrator assigned to the application group, delivery group and catalog, the administrator cannot see application instances within director.
• If the application is published directly from the delivery group and granted the same scope rights, the administrator can see application instances within Director.
• Custom administrators cannot see application instances unless they are scoped to "all" and have at least read-only administrator rights.
• It seems that if any scope other than "all" is used, the administrator cannot see application instances from the application group.
• If the scope of an administrator is not "All" (the default created scope), and they try to view application instances of any applications published via Application -> Application Group -> Delivery group, nothing shows in application instances. 

This is a known issue.

Workaround:
Change Scope of the custom admin to "All" and give "read-only" rights.

---

Problem Cause

Customer may notice that when an application is published from an application group, this application instance will not be listed in director.
 
The main factor for this behavior is that the admin logging into director is assigned a custom scope. 
 
This is due to the fact that the coding required to facilitate the filtering of application group application is not included in the current or any release of the Virtual Desktop and App product. 
 
This causes the monitor service to be unaware of any  brokering of application related to  application  groups.
 
Monitor database directly associates an application with a desktop group, whereas the association can be via the intermediary app group.
 
Since Monitor database doesn't have that information on the application groups all application instances that aren't directly associated with the delivery group in the custom admin's scope are filtered out.
 
This is not an issue when a full admin is logged into director.