Our guide to automating Google Workspace onboarding and offboarding builds the leaver process around a dry run. planOffboarding reads the account and writes a plan to a sheet, a person reviews it, and applyOffboarding(token) executes "exactly that plan and nothing else". It stops on the first failure so you are left with "a knowable state instead of a mystery".

I ran those two functions, unchanged, against a fake Admin SDK with one invented leaver: two groups, one phone, one license. The helpers the guide leaves to the reader ( writePlanToSheet , execute , audit ) were written the plainest way it describes them. Three things happened that the guide's promises do not cover.

A failed plan cannot be finished. The tokens step threw a transient Backend Error on the first run. The second run started again at step 1, signed out and suspended a second time, then stopped on the group the first run had already removed. The third run stopped in the same place.…