Hi (brace yourself..)
Logs are stored per-profile and if you select View Log for a Group the request is cascaded down to the profile/s in it (to query their [profilename]_Logs.ini to find the name and location of the most-recent log, then ask Windows to open that file). In this case there is only one profile in each Group - and it's the same one in all of them, so if you select all four Groups, and then Task menu > View [most-recent] Log, the request generates 4 calls to Windows to open the same HTML file four times. This will be the most-recent log for the profile that is viewable (note that you can't View Log for a run that is still in process - that info is still in RAM and/or temp files)
Which actual log is displayed (four times...) will depend on the timing, and which run of the profile has finished (and created a log file) this time around (if any). But whatever happens, you'll get four logs all the same because it's four calls to a single profile's INI that delivers the same answer to the 'most-recent' question four times.
If you select all four Groups at the end and click Task > View [most-recent] Log, the same thing will happen but now it will be a different (most-recent) log, because the profiles have all finished and it will all be stored on disk. Hence you'll get 4 copies of the most-recent log (the one generated by the latest run c/o Group #4)
Given that it's the same common profile creating all the logs, you could expand one of the Groups (doesn't matter which), right-click the profile and select View Log > cascaded sub-menu of all logs available (though the sub-menu entries will only display the date/time to tell you which is which). Note that the right-click option only gets you to View [most-recent] Log if you right-click a Group, because there's no way to generate multiple sub-menus at once of the potentially-multiple logs in a Group for the potentially-multiple profiles inside it - so the possibility it might need to try is locked off in the Group context)
Basically, the trick in this situation is to avoid calling for a log via the Groups (certainly via all four groups at once, because what you generate is four 'most-recent log' calls to the same profile...). What you could do is configure the profile to display the log at the end if it's a manual run, and each one would open when it's ready. If you need to open an older log, right-click the profile and select one from the menu. But there's no way to view (ask for) the last four logs for a single profile in a single action.
Logs are stored per-profile and if you select View Log for a Group the request is cascaded down to the profile/s in it (to query their [profilename]_Logs.ini to find the name and location of the most-recent log, then ask Windows to open that file). In this case there is only one profile in each Group - and it's the same one in all of them, so if you select all four Groups, and then Task menu > View [most-recent] Log, the request generates 4 calls to Windows to open the same HTML file four times. This will be the most-recent log for the profile that is viewable (note that you can't View Log for a run that is still in process - that info is still in RAM and/or temp files)
Which actual log is displayed (four times...) will depend on the timing, and which run of the profile has finished (and created a log file) this time around (if any). But whatever happens, you'll get four logs all the same because it's four calls to a single profile's INI that delivers the same answer to the 'most-recent' question four times.
If you select all four Groups at the end and click Task > View [most-recent] Log, the same thing will happen but now it will be a different (most-recent) log, because the profiles have all finished and it will all be stored on disk. Hence you'll get 4 copies of the most-recent log (the one generated by the latest run c/o Group #4)
Given that it's the same common profile creating all the logs, you could expand one of the Groups (doesn't matter which), right-click the profile and select View Log > cascaded sub-menu of all logs available (though the sub-menu entries will only display the date/time to tell you which is which). Note that the right-click option only gets you to View [most-recent] Log if you right-click a Group, because there's no way to generate multiple sub-menus at once of the potentially-multiple logs in a Group for the potentially-multiple profiles inside it - so the possibility it might need to try is locked off in the Group context)
Basically, the trick in this situation is to avoid calling for a log via the Groups (certainly via all four groups at once, because what you generate is four 'most-recent log' calls to the same profile...). What you could do is configure the profile to display the log at the end if it's a manual run, and each one would open when it's ready. If you need to open an older log, right-click the profile and select one from the menu. But there's no way to view (ask for) the last four logs for a single profile in a single action.