fix: add error handling for org member invite during team migration

[eunjae-lee]

What does this PR do?

When migrating teams to an organization, if inviting team members to the org fails (e.g. profile creation error, unique constraint violation), the entire migration could silently leave teams moved but with no org-level memberships created. This results in members appearing on the team members page but not on the org members page.

Two changes:

1. createTeams.handler.ts (moveTeam): Wraps inviteMembersWithNoInviterPermissionCheck in a try-catch so that a failed invite does not block the rest of the migration (redirects, subscription cancellation, subsequent team migrations). Adds logging for invite attempt details, success, and failure with full error context.

2. inviteMember/utils.ts (handleExistingUsersInvites): Changes Promise.all → Promise.allSettled for the org invite path. Previously, if creating a profile/membership for any single user failed, the entire batch would reject and no users would get org memberships. Now each user is processed independently — failures are logged per-user while successful invites still proceed.

Note: This PR adds resilience and diagnostic logging to help identify the root cause of missing org members after migration. The exact trigger for the original failure is not yet confirmed — these logs will surface it on next reproduction.

Updates since last revision

• Removed PII (email addresses) from all log statements. Logs now identify users by userId only, not by email.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

1. Seed a local DB (yarn db-seed) — use teampro@example.com / teampro
2. As instance admin, create a new org via /settings/organizations/new with handover flow
3. As teampro@example.com, resume onboarding and select all teams to migrate
4. After completion, check /settings/organizations/<orgslug>/members — previously no members would appear
5. Check server logs (NEXT_PUBLIC_LOGGER_LEVEL=3) for the new log lines:
   • "Inviting team members to org" with member count and team/org IDs
   • "Successfully invited team members to org" or "Failed to invite team members to org during migration" with error details
   • Per-user "Failed to invite existing user to organization" (identified by userId) if individual invites fail

Human Review Checklist

• Swallowed errors in moveTeam: The catch block logs but does not re-throw. This means the org creation succeeds even if ALL member invites fail — the user sees no error, just missing members. Is this the right tradeoff vs. failing the whole migration?
• Promise.allSettled downstream safety: Verify that existingUsersWithMembershipsNew (now filtered to only fulfilled results) is safe for seat tracking and email sending logic below it.
• No tests added: This is an error-handling + logging change; consider whether integration tests covering the migration failure path should be added.
• Logging without emails: Failed user invites are now identified only by userId (PII removed). Confirm this is sufficient for debugging — correlating userId to email requires a separate DB lookup.

---

Link to Devin run: https://app.devin.ai/sessions/cfe7ebd1961740cea3181ccfb7e61f1e
Requested by: @eunjae-lee

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[cubic-dev-ai]

2 issues found across 2 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/trpc/server/routers/viewer/teams/inviteMember/utils.ts">

<violation number="1" location="packages/trpc/server/routers/viewer/teams/inviteMember/utils.ts:710">
P1: Rule violated: **Avoid Logging Sensitive Information**

Remove or redact the email from the error log payload to avoid logging PII.</violation>
</file>

<file name="packages/trpc/server/routers/viewer/organizations/createTeams.handler.ts">

<violation number="1" location="packages/trpc/server/routers/viewer/organizations/createTeams.handler.ts:260">
P1: Rule violated: **Avoid Logging Sensitive Information**

Do not log member emails in org migration logs; emails are PII and must be excluded or redacted per the logging rule.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[github-actions]

Devin AI is addressing Cubic AI's review feedback

New feedback has been sent to the existing Devin session.

View Devin Session

---

✅ Pushed commit 566ba28