This article explains the expected behavior of offboarding steps in relation to suspended users in Google Workspace and the automatic 1-hour delay CloudM applies for unsuspend actions and the rationale behind it.
Behavior
Any offboarding step that requires a suspended user to be unsuspended (to allow the action to take place) now includes a built-in 1-hour delay.
This delay is crucial for ensuring that all data has fully propagated across CloudM and Google Workspace before the next action is performed.
Manual Override
Caution: Manual override may cause propagation issues
You can manually trigger the action to bypass the delay, but this may result in errors as some data might not have fully propagated.
Need help? Contact CloudM Support