When attempting to remove or add out of office settings for a user the setting is not committed, and the users out of office can also not be removed from the out of office list.
The issue can be detected by executing the scripts below in sequence. It has been noted that the cause of the issue is a possible design fault in one of the workflows which would require that you navigate through your workflows in order to rectify the faulty design to eliminate the cause. After using the scripts below you will need to log a support ticket to obtain an additional script which can then be used to clean these users out. However, you will need to provide the result of the scripts below in this ticket as reference.
The faulty design specified is for example: when a workflow is set up to use a destination user, but the user that was added is not a group or role, but it has been chosen as such inside of the destination user slot.
Script Executions to trace this issue
Select [A1].ActionerName as OOFUser, [A1].ActionerType as ActionerTypeID,
CASE WHEN [A1].ActionerType = 1 THEN '[User]' ELSE '[Group]' END as ActionerType, CASE WHEN [A1].Status = 1 THEN '[OUT of Office]' ELSE '[IN Office]' END as Status, [A2].ActionerName as OOFDestination, [A2].ActionerType as ActionerTypeID, CASE WHEN [A2].ActionerType = 1 THEN '[User]' ELSE '[Group]' END as DestActionerType From [Server].[Actioner] [A1] Join [Server].[ActionerShare] [AS] On [AS].ActionerID = [A1].[ID] Join [Server].[ActionerShareWorktype] [ASWT] On [ASWT].ActionerShareID = [AS].[ID] Join [Server].[Worktype] [WT] On [WT].[ID] = [ASWT].WorktypeID Join [Server].[WorktypeShare] [WTS] On [WTS].WorktypeID = [WT].[ID] Join [Server].[Actioner] [A2] On [A2].[ID] = [WTS].ActionerID
After performing the scripts above in sequence, you should have been able to pinpoint the problematic users. The last step to perform would be to clear these users out, for that you will need to obtain a removal script by logging a support ticket and providing the results of the above as well as this KB as reference. The removal process will the be run through with you by a support engineer via the logged support ticket.