plandex-ai/plandex · error

Error deleting invite:

Error message

Error deleting invite: 

What it means

DeleteInviteHandler calls db.DeleteInvite(inviteId, nil) after authorization; if that mutation fails it responds 500 'Error deleting invite: <err>'. The permission checks already passed, so this is purely a persistence-layer failure (the nil transaction argument means it runs outside an explicit transaction).

Source

Thrown at app/server/handlers/invites.go:402

	}

	// ensure current user can remove target invite
	removePermission := shared.Permission(strings.Join([]string{string(shared.PermissionRemoveUser), invite.OrgRoleId}, "|"))

	invitePermission := shared.Permission(strings.Join([]string{string(shared.PermissionInviteUser), invite.OrgRoleId}, "|"))

	if !(auth.HasPermission(removePermission) ||
		(auth.User.Id == invite.InviterId && auth.HasPermission(invitePermission))) {
		log.Printf("User does not have permission to remove invite with role: %v\n", invite.OrgRoleId)
		http.Error(w, "User does not have permission to remove invite with role: "+invite.OrgRoleId, http.StatusForbidden)
		return
	}

	err = db.DeleteInvite(inviteId, nil)

	if err != nil {
		log.Printf("Error deleting invite: %v\n", err)
		http.Error(w, "Error deleting invite: "+err.Error(), http.StatusInternalServerError)
		return
	}

	log.Println("Successfully deleted invite")
}

View on GitHub (pinned to e2d772072e)

Solutions

1. Check the server log for the exact DB error after 'Error deleting invite:'
2. Retry the delete; if the invite was concurrently removed, the 404 path will tell you
3. Verify DB health (locks, connectivity) and application user write privileges on invites

if resp.StatusCode >= 500 {
	await sleep(backoff)
	// retry delete; a subsequent 404 means it was concurrently removed
}

try {
	await client.deleteInvite(inviteId)
} catch (e) {
	if (e.status >= 500) { await retryWithBackoff(() => client.deleteInvite(inviteId)); return }
	throw e
}

When it happens

Trigger: DELETE /invites/{inviteId} when the DELETE statement fails: DB connection dropped, deadlock/lock timeout on the invites row, constraint violation, or the row disappeared concurrently between the GetInvite read and the delete.

Common situations: Database failover mid-request; concurrent deletion by another admin (row already gone, depending on driver error semantics); long-running transaction holding a lock on the invites table.

Related errors

• error getting current plan state params: %v
• error getting contexts: %v
• error validating project
• error validating plan membership
• Error validating org membership:

AI-assisted analysis of plandex-ai/plandex@e2d772072e (2026-09-05). Data as JSON: /api/errors/3590befce3f0c0c1. Report an issue: GitHub.