About a week ago I reported this bug in the other 'Group' thingy but it has now disappeared as other issues have pushed it down the list.
Here we have another incidence of the problem.
The response to my last post from the developers was that they were 'investigating' the problem.
Any chance of being told what the investigations revealed?
Here are the logs taken before a restart.
1512.Proclaim Logs.zip
As usual a restart restarted the operation.
