fix: handle email uniqueness conflict during SaaS user provisioning #19

Merged
nrupard merged 1 commit from fix/db-error into main 2026-03-25 15:57:59 +01:00
Member

The upsert used ON CONFLICT (id) but failed when a different user_id
tried to insert an email already belonging to another user, violating
the users_email_key constraint. Now retries with a unique fallback
email ({user_id}@saas.local) if the initial insert fails.

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

The upsert used ON CONFLICT (id) but failed when a different user_id tried to insert an email already belonging to another user, violating the users_email_key constraint. Now retries with a unique fallback email ({user_id}@saas.local) if the initial insert fails. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The upsert used ON CONFLICT (id) but failed when a different user_id
tried to insert an email already belonging to another user, violating
the users_email_key constraint. Now retries with a unique fallback
email ({user_id}@saas.local) if the initial insert fails.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
nrupard deleted branch fix/db-error 2026-03-25 15:57:59 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
a8n-tools/rusty-links!19
No description provided.