We deliberately don't auto-poll the profiles for status all that often to keep the footprint light. Remember also that any Scheduled (or other command-line trigger) runs of profile/s (for example, OnLogin) are not run by the instance of Pro that Starts With Windows (another* instance of Pro is opened, used and closed). Hence the SWW instance likely isn't running the profiles in question. And a Minimized instance doesn't auto-poll profiles at all (AFAIK) because there's nowhere to display the info and it adds to the load on the PC for (arguably) no apparent gain while Minimized
Problem is, if we added a 'prod' to auto-poll all profiles on Show and they happened to be up-to-date already, and the user has a lot of profiles, we'd get complaints the UI was now slower to 'visibilize' (for no apparent benefit to that user)
The forthcoming V7 may well improve this because it has code to monitor (and inter-act with) profiles run by the same user in another instance of Pro, so hopefully updates those values in real time.
* given that there may not be a Start With Windows instance, this is an independent process
Problem is, if we added a 'prod' to auto-poll all profiles on Show and they happened to be up-to-date already, and the user has a lot of profiles, we'd get complaints the UI was now slower to 'visibilize' (for no apparent benefit to that user)
The forthcoming V7 may well improve this because it has code to monitor (and inter-act with) profiles run by the same user in another instance of Pro, so hopefully updates those values in real time.
* given that there may not be a Start With Windows instance, this is an independent process