MGNLUI-2966, we've implemented a fix that handles many cases where an asynchronously running action changes a tree without notifying the view. Basically, we track the location changes and if the browser sub-app sees that the new location is its own, it refreshes itself.
However, this fix doesn't work in cases where:
- there is no location change (e.g. an asynchronously running delete action not using work flow)
- the change occurs in a different session (e.g. another user approves the work flow)
There are several ways to fix this. In discussions, it seems that a combination of observation and push support would help, but also low-level conventions such as requiring an asynchronously running action to call a method once it completes, which in turn notifies apps, could be part of a solution.