feat: added retry payment feature #4403
Open
+249
−38
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
When sending a payment, if the first-hop local channel can't handle it (e.g., HTLC slots full, amount exceeds current max, temporary balance constraint), LDK previously returned
APIError::ChannelUnavailablewhich blacklisted the channel SCID inpreviously_failed_channels, preventing retries from using it. This PR introduces a newAPIError::ChannelBusyvariant for these temporary local failures (originating fromChannelError::Ignoreinsend_htlc_and_commit). UnlikeChannelUnavailable,ChannelBusydoes not blacklist the channel, so the router can still select it on retry once the transient condition clears. This is the first step toward addressing #4161 — enabling LDK to automatically retry payments through temporarily-congested channels rather than immediately giving up on them.Closes: #4161