Remove user data after 28 days from last updated #588
Conversation
This file contains 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
StevenLeighton21
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We run the db sweeper every hour, and it removes records created at 28.days.ago
Which means records live 28 days + up to 59 minutes
We delete files using a 28 day retention policy managed by S3, which appears to delete at 00:00 on the 28th day, so it functionally keeps files for 27 days + minutes until midnight
This seems to leave an edge case where you can use save & return to return to your form on the morning of the 28th day, complete your submission successfully and see no errors.
We will see a failed submission where the S3 bucket returns 404 results for the attachments you uploaded 28 days ago. It's possible this isn't the (or the only) reason this can happen but this should prevent one failure case.