Skip to content

fix: run batch member delete asynchronously ⏰#882

Merged
ramiAbdou merged 1 commit into
mainfrom
rami/batch
Sep 24, 2025
Merged

fix: run batch member delete asynchronously ⏰#882
ramiAbdou merged 1 commit into
mainfrom
rami/batch

Conversation

@ramiAbdou
Copy link
Copy Markdown
Member

Description ✏️

This PR moves the batch member deletion to run completely asynchronously since it can take 30+ minutes to complete for a long list.

Type of Change 🐞

  • Feature - A non-breaking change which adds functionality.
  • Fix - A non-breaking change which fixes an issue.
  • Refactor - A change that neither fixes a bug nor adds a feature.
  • Documentation - A change only to in-code or markdown documentation.
  • Tests - A change that adds missing unit/integration tests.
  • Chore - A change that is likely none of the above.

Checklist ✅

  • I have done a self-review of my code.
  • I have manually tested my code (if applicable).
  • I have added/updated any relevant documentation (if applicable).

@ramiAbdou ramiAbdou self-assigned this Sep 24, 2025
@ramiAbdou ramiAbdou marked this pull request as ready for review September 24, 2025 04:20
@ramiAbdou ramiAbdou merged commit 40d4dd4 into main Sep 24, 2025
3 checks passed
@ramiAbdou ramiAbdou deleted the rami/batch branch September 24, 2025 04:21
Copy link
Copy Markdown
Contributor

@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 PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

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

slackId: student.slackId,
});
}
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bug: Missing Error Handling in Batch Member Removal

The batchRemoveMembers function is missing the try-catch error handling and Sentry reporting from the original removeMembers function. Without it, database operations and subsequent job queueing failures won't be caught or reported, leading to unhandled exceptions and reduced observability of member removal issues.

Fix in Cursor Fix in Web

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