We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Invoices and outgoing payments use the same webhook id as withdrawal transfer ids across attempts, which will result in a TransferExists TB error on retries. https://github.com/interledger/rafiki/blob/main/packages/backend/src/open_payments/invoice/service.ts#L207 Unique transfer ids should be used on each attempt (unless Tigerbeetle supported two-phase commit transfers without a timeout).
TransferExists
If we had a limit on webhook retries, then it might be fine to use a single transfer with a timeout corresponding to that limit.
The text was updated successfully, but these errors were encountered:
reserved/accepted
pending/posted
unit
ledger
wilsonianb
Successfully merging a pull request may close this issue.
Invoices and outgoing payments use the same webhook id as withdrawal transfer ids across attempts, which will result in a
TransferExists
TB error on retries.https://github.com/interledger/rafiki/blob/main/packages/backend/src/open_payments/invoice/service.ts#L207
Unique transfer ids should be used on each attempt (unless Tigerbeetle supported two-phase commit transfers without a timeout).
If we had a limit on webhook retries, then it might be fine to use a single transfer with a timeout corresponding to that limit.
The text was updated successfully, but these errors were encountered: