CAB Workbench not updating Change approved during meeting

[MGanon]

I am trying to understand why approving a Change during a CAB Workbench meeting returned a warning message to approve the Change when attempting to navigate to the next Change record.

I approved the first Change during the meeting using the Approve button in the upper right of the meeting window. The state of the Change shifted to Scheduled and the option to approve or reject disappeared as a meeting option indicating to me that the change was approved. When I navigated to the the next Change on the agenda, I received a warning:

   "Confirmation
    The current agenda item has not been approved.
    Do you want to move to the next item?
    Cancel | OK"

Looking at the agenda item on another screen, I noticed that the state of that agenda item didn't change. I would have expected it to update from Pending to Complete.

Am I missing something?

[john_duchock]

it seems that @MGanon has resolved his issue by reverting some objects back to OOTB...  We are having the same issue and reverting objects to original state did not help us (but i am not sure i looked at all objects).

Our work-around is to have users refresh the page after each approval during CAB...  a bit burdensome, but workable...

I did see THIS KB ARTICLE, but we are on Rome p4, so we should already have the "fix"

I guess we will have to create a new HI ticket 😞

[MGanon]

I was not able to resolve the issue but the priority to resolve was reduced. The issue still exists along with this issue too: https://community.servicenow.com/community?id=community_question&sys_id=38e4665ddb65815007ab8263059619c5

[MGanon]

Accessing different browsers had no affect. I thought that I posted that update here but apparently only posted to the related issue post: https://community.servicenow.com/community?id=community_question&sys_id=38e4665ddb65815007ab8263059619c5

[MGanon]

The system has some customization that is causing unexpected behavior.

[john_duchock]

@MGanon  Can you tell me what customizations were made?

we are having the same issue...