-
Notifications
You must be signed in to change notification settings - Fork 4.2k
feat(router): Add revenue recovery retry algorithm type and data columns to business_profile table #7772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+185
−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
Changed Files
|
Aprabhat19
reviewed
Apr 9, 2025
Aprabhat19
reviewed
Apr 9, 2025
Aprabhat19
reviewed
Apr 15, 2025
Aprabhat19
reviewed
Apr 15, 2025
Aprabhat19
reviewed
Apr 15, 2025
Aprabhat19
reviewed
Apr 15, 2025
Co-authored-by: Amisha Prabhat <[email protected]>
Aprabhat19
previously approved these changes
Apr 15, 2025
ShankarSinghC
previously approved these changes
Apr 17, 2025
61dc5a6
Aprabhat19
reviewed
Apr 23, 2025
Aprabhat19
reviewed
Apr 23, 2025
Aprabhat19
approved these changes
Apr 23, 2025
ShankarSinghC
approved these changes
Apr 24, 2025
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.
Type of Change
Description
This PR adds support for configuring revenue recovery retry algorithms at the business level. When a new billing connector is created, the columns are updated with Monitoring as the default algorithm type and the current timestamp. It introduces two new columns in the
business_profile
table:revenue_recovery_retry_algorithm_type
(enum)Specifies the retry algorithm type to be used for revenue recovery. This value will be used to determine the retry strategy for a transaction and will be included in the tracking data for the process tracker.
Supported values:
Cascading
– Exponential retry strategy that increases the interval between retries after each attempt.Smart
– Data-driven retry approach that adapts dynamically based on historical performance and success rates.Monitoring
(default) – Passive mode with no active retries; used to observe behavior without influencing outcomes.revenue_recovery_retry_algorithm_data
(JSON)A
serde_json
column to store additional data for the configured algorithm.In
Monitoring
mode, it includes:Additional Changes
Motivation and Context
How did you test it?
Curl
revenue_recovery_retry_algorithm_type and revenue_recovery_retry_algorithm_data columns added in business_profile table.

Curl 2
When a new billing processor is created, the revenue_recovery_retry_algorithm_type and revenue_recovery_retry_algorithm_data columns in the business_profile table are updated to Monitoring and the current timestamp by default.
Checklist
cargo +nightly fmt --all
cargo clippy