Remove unused reimbursement_reminders_2025_01_21
#12963
Merged
+2
−2
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR removes the fully-enabled feature flag reimbursement_reminders_2025_01_21 that was gating the scheduling of reimbursement reminder jobs. The reminder functionality is now always enabled for all reimbursement reports.
Changes:
- Removed conditional feature flag checks for scheduling
OneDayReminderJobandSevenDaysReminderJob - Both reminder jobs are now unconditionally scheduled when a new reimbursement report is created
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Mohamad-Mortada
approved these changes
Feb 13, 2026
Mohamad-Mortada
deleted the
mxg-remove-unused-reimbursement_reminders_2025_01_21
branch
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.
This feature flag is fully enabled!