Skip to content

fix: handle fkey constraint violations in organization merge with llm#3601

Merged
skwowet merged 2 commits into
mainfrom
bugfix/merge-member-with-llm
Nov 13, 2025
Merged

fix: handle fkey constraint violations in organization merge with llm#3601
skwowet merged 2 commits into
mainfrom
bugfix/merge-member-with-llm

Conversation

@skwowet
Copy link
Copy Markdown
Collaborator

@skwowet skwowet commented Nov 13, 2025

Note

Adds try/catch to skip on foreign key constraint violations when inserting organization no-merge suggestions, with improved logging.

  • Merge Suggestions Worker (services/apps/merge_suggestions_worker/src/activities/organizationMergeSuggestions.ts):
    • Handle foreign key constraint (23503) when calling addOrgNoMerge by logging and skipping instead of failing.
    • Improve debug message to specify the suggestions array must contain exactly two IDs.
    • Add error logging and rethrow for non-FK errors.

Written by Cursor Bugbot for commit 513ed15. This will update automatically on new commits. Configure here.

@skwowet skwowet self-assigned this Nov 13, 2025
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

2 similar comments
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on December 12

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

  • feat: add user authentication (CM-123)
  • feat: add user authentication (IN-123)

Projects:

  • CM: Community Data Platform
  • IN: Insights

Please add a Jira issue key to your PR title.

@skwowet skwowet merged commit 94eec6e into main Nov 13, 2025
16 checks passed
@skwowet skwowet deleted the bugfix/merge-member-with-llm branch November 13, 2025 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant