[Team Deletions] effective scheduling - #6615
Open
aerosol wants to merge 4 commits into
Open
Conversation
aerosol
changed the title
aerosol
changed the title
…s-deletions-intervals
…s-deletions-intervals
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On top of #6613 this PR implements the core deletion eligibility logic including the background worker (tested but kept inactive for now).
A daily worker seeks for eligible teams and bulk-inserts
team_deletion_schedulesrows.Additional Paddle webhooks checks are planted to cancel any pending deletions upon subscription renewal.
Schema/migration change (deleted->completed rename) backported to previous branches in the stack.