plandex-ai/plandex · error

error getting invite for org user: %v

Error message

error getting invite for org user: %v

What it means

After deleting the org user inside the same transaction, the handler looks up an active invite for the deleted user's email via db.GetActiveInviteByEmail. If that query errors (not 'no rows' — an actual failure), the tx is rolled back and the wrapped error is returned as HTTP 500.

Source

Thrown at app/server/handlers/users.go:201

			http.Error(w, "Cannot delete the only org owner", http.StatusForbidden)
			return
		}
	}

	err = db.WithTx(r.Context(), "delete org user", func(tx *sqlx.Tx) error {

		err = db.DeleteOrgUser(auth.OrgId, userId, tx)

		if err != nil {
			log.Println("Error deleting org user: ", err)
			return fmt.Errorf("error deleting org user: %v", err)
		}

		invite, err := db.GetActiveInviteByEmail(auth.OrgId, auth.User.Email)

		if err != nil {
			log.Println("Error getting invite for org user: ", err)
			return fmt.Errorf("error getting invite for org user: %v", err)
		}

		if invite != nil {
			err = db.DeleteInvite(invite.Id, tx)

			if err != nil {
				log.Println("Error deleting invite: ", err)
				return fmt.Errorf("error deleting invite: %v", err)
			}
		}

		return nil
	})

	if err != nil {
		log.Println("Error deleting org user: ", err)
		http.Error(w, "Error deleting org user: "+err.Error(), http.StatusInternalServerError)
		return

View on GitHub (pinned to e2d772072e)

Solutions

1. Check the wrapped cause; distinguish real errors from sql.ErrNoRows (which is handled as nil invite).
2. Verify DB connectivity and pool health.
3. Confirm the invites table/migrations exist in the environment.
4. Retry the deletion if the failure was transient (connection, context canceled).

Example fix

// before
invite, err := db.GetActiveInviteByEmail(auth.OrgId, auth.User.Email)
if err != nil { return fmt.Errorf("error getting invite for org user: %v", err) }
// after
invite, err := db.GetActiveInviteByEmail(auth.OrgId, auth.User.Email)
if errors.Is(err, sql.ErrNoRows) {
    return nil
} else if err != nil {
    return fmt.Errorf("error getting invite for org user: %v", err)
}

// Go
if err := db.PingContext(ctx); err != nil {
    return fmt.Errorf("db unavailable: %w", err)
}

invite, err := db.GetActiveInviteByEmail(auth.OrgId, auth.User.Email)
if errors.Is(err, sql.ErrNoRows) {
    return nil // no invite; not an error
}
if err != nil {
    return fmt.Errorf("error getting invite for org user: %v", err)
}

When it happens

Trigger: The invite lookup query fails: DB unreachable, connection pool exhaustion, SQL/schema error in the invites table, or cancellation of the request context mid-transaction.

Common situations: Database outage during user offboarding; invites schema migration missing; context canceled by client disconnect mid-tx (context canceled errors).

Understand the failure class

Background: Database query failed: Internal Server Error 500s wrapping SQL, Prisma, and connection failures — what to check first — this error's family across 16 libraries.

Related errors

• error adding plan context tokens: %v
• error adding org member: %v
• error listing org roles: %v
• error adding org user: %v
• error getting plan config: %v

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