Hey @godwin.owonam
I apologize for the documentation not clearly explaining the changes in subsession status.
After calling ssClient.closeAllSubsessions(), the subsession’s status becomes SubsessionStatus.Closing.
This is because if there is a waitSeconds option in ssClient.openSubsessions, it is intended to wait for users still in the subsession to leave. So, when ssClient.closeAllSubsessions() is called, the subsession’s status changes from SubsessionStatus.InProgress to SubsessionStatus.Closing and finally to SubsessionStatus.Closed .
You can monitor this state change by listening to the subsession-state-change event.
Thanks
Vic