topic Re: Google Classroom Ownership Transfer Stuck in Peer-Peer Topics

Google Classroom Ownership Transfer Stuck

Bill_Gibson — Tue, 04 Mar 2025 20:57:41 GMT

We attempted to transfer the ownership of some Google Classrooms after unsuspending the owner's account...then re-suspending it.
It seems that the ownership transfer process is now stuck.

Command 1:
gam user USER-HERE accept classroominvitations ids ID-HERE
OUTPUT>>>
User:USER-HERE, Accept 1 Classroom Invitation
User: USER-HERE, Classroom Invitation:ID-HERE, Accept Failed: @OwnershipTransferInProgress Ownership of this class is already being transferred

Command 2:
gam update course COURSE-HERE owner USER-HERE
OUTPUT>>>
Course: COURSE-HERE, Update Failed: @PendingInvitationExists Someone has already been invited to take ownership of the course

Re: Google Classroom Ownership Transfer Stuck

Kim_Nilsson — Wed, 16 Apr 2025 13:57:52 GMT

Well, the first command already told you that someone had tried to transfer the Classroom, and then the API doesn't allow you to transfer to someone else. Only viable option, I think, would be to reset the password of the Classroom owner and remove the transfer request, which I think can't be done via API, and then send a new transfer request. Either with GAM or manually in Classroom, as you are now already logged in as the user.

Re: Google Classroom Ownership Transfer Stuck

Bill_Gibson — Mon, 07 Apr 2025 16:20:03 GMT

Current status: Took over the account, and attempted to cancel the transfer request, transfer again, transfer to another person. All fail with an error message.
I opened a support case a month ago, it's P2 with an escalation...with seemingly no progress beyond getting an internal case opened. 😭

Re: Google Classroom Ownership Transfer Stuck

Kim_Nilsson — Wed, 16 Apr 2025 13:59:30 GMT

Tough break. It needs to be possible to cancel a transfer, or it should auto-cancel itself after a while, or at least be allowed to transfer to someone else if the first request isn't confirmed, which at the same time, of course, should invalidate the first request.