Schedule and monitor stale draft cleanup in the backend - #535
Open
harryjupiter148 wants to merge 2 commits into
Open
Schedule and monitor stale draft cleanup in the backend#535harryjupiter148 wants to merge 2 commits into
harryjupiter148 wants to merge 2 commits into
Conversation
Contributor
|
@harryjupiter148 kindly fix |
…o 22.x - draft.service.spec.ts was not updated when ConfigService was added to DraftService's constructor in 65e99d3, causing NestJS DI to throw at compile time and all tests in that suite to fail with exit code 1 - Bump CI matrix node-version from 20.x (deprecated) to 22.x (LTS) to resolve the 'Node.js 20 is deprecated, being forced to Node.js 24' warning and ensure a predictable runtime
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
2 participants
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.
Summary
Implemented scheduled cleanup for stale invoice drafts so expired drafts are automatically removed from storage instead of accumulating indefinitely.
The cleanup job is now wired into the running backend with configurable retention behavior and logging to make cleanup activity visible to maintainers and easier to verify operationally.
Related Issue(s)
Closes #519
Type of Change
Description
Testing Evidence
Checklist