plandex-ai/plandex · error

Error getting invite:

Error message

Error getting invite: 

What it means

InviteUserHandler wraps any error from db.GetActiveInviteByEmail(auth.OrgId, req.Email) into an HTTP 500 prefixed with 'Error getting invite: '. This lookup guards against duplicate active invites; the error means the query itself failed (DB connectivity, SQL error, scan failure), not that an invite exists. It is a server-side data-layer failure.

Source

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

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

		if isMember {
			log.Println("User is already a member of org")
			http.Error(w, "User is already a member of org", http.StatusBadRequest)
			return
		}
	}

	// ensure invite isn't already active
	invite, err := db.GetActiveInviteByEmail(auth.OrgId, req.Email)

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

	if invite != nil {
		log.Println("Invite already exists")
		http.Error(w, "Invite already exists", http.StatusBadRequest)
		return
	}

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

		err = db.CreateInvite(&db.Invite{
			OrgId:     auth.OrgId,
			OrgRoleId: req.OrgRoleId,
			Email:     req.Email,
			Name:      req.Name,
			InviterId: currentUserId,
		}, tx)

View on GitHub (pinned to e2d772072e)

Solutions

1. Read the server log line with the same message to identify the wrapped DB error
2. Verify DB connectivity and that recent schema migrations for invites completed
3. Check connection pool settings and for leaked connections under load
4. Retry the invite request once the database issue is resolved

Example fix

// before
if err != nil {
    http.Error(w, "Error getting invite: "+err.Error(), http.StatusInternalServerError)
    return
}
// after
if err != nil {
    log.Printf("Error getting invite: %v\n", err)
    writeApiError(w, shared.ApiError{Type: shared.ApiErrorTypeOther, Status: http.StatusInternalServerError, Msg: "Failed to check existing invites, please try again"})
    return
}

// client: check pending invites before inviting
invites, err := listPendingInvites(orgId)
if err == nil {
    for _, inv := range invites {
        if strings.ToLower(inv.Email) == strings.ToLower(email) {
            return fmt.Errorf("invite for %s already pending", email)
        }
    }
}

func isGetInviteServerError(statusCode int, body string) bool {
    return statusCode == http.StatusInternalServerError && strings.Contains(body, "Error getting invite")
}

resp, err := client.Post(inviteUrl, jsonBody)
body, _ := io.ReadAll(resp.Body)
if resp.StatusCode == 500 && strings.Contains(string(body), "Error getting invite") {
    return fmt.Errorf("transient DB error checking invites; retry with backoff: %s", body)
}

When it happens

Trigger: POST to the invite-user endpoint (after membership validation passes) where the GetActiveInviteByEmail SELECT fails: Postgres down, connection pool exhausted, query timeout, canceled request context, invites table missing, or row-scan/type mismatch after a schema change.

Common situations: Database migrations partially applied so the invites table/columns changed; transient Postgres restarts; connection leaks exhausting the pool under load; clients aborting requests causing context cancellation mid-query.

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 validating org membership:
• Error listing invites:
• error getting current plan state params: %v
• error getting contexts: %v
• error validating project

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