### Problem In CustomersDot admin panel, there exists the functionality to "Perform reconciliation" manually. However, this doesn't appear to support retrying a failed reconciliation, such as in the event of payment declined errors. Clicking this on a failed reconciliation returns simply > Reconciliation has already been executed This would be from `ReconciliationService#excute` [bailing out when Reconciliaton.fulfilled?](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4c0f5127e8029244232e7f32eb6452dbf23ec67b/app/services/reconciliation_service.rb#L15-18) is true, with `fulfilled?` simply being [the presence of](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4c0f5127e8029244232e7f32eb6452dbf23ec67b/app/models/reconciliation.rb#L137-138) `reconcile_done_at` on the reconciliation, which, barring any internal errors, seems to always be set after a reconciliation is processed, regardless of success state (which _is_ handled with [`Reconciliation#successful?`](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4c0f5127e8029244232e7f32eb6452dbf23ec67b/app/models/reconciliation.rb#L141)) Contrast this with the job that reprocesses reconciliations failed due to declines and other payment failures, `RetryDeclinedReconciliationJob`, after it locates eligible reconciliations to retry, it [clears that and other attributes](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4c0f5127e8029244232e7f32eb6452dbf23ec67b/app/jobs/retry_declined_reconciliation_job.rb#L13), allowing `ReconciliationService` to process it again. The main problem here surfaces when a customer adds a new card due to a failure, and it fails again, they have to [update the payment method](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4c0f5127e8029244232e7f32eb6452dbf23ec67b/app/controllers/payment_methods_controller.rb#L17-25) yet again in order to trigger that job, which may not be practical for them if the card they want to use is already present. Kind of a minor inconvenience, but somewhat circular in nature if the customer just handles the cause of the failure on their end and lets support team know. This can also result in a behavior where `500` errors are thrown with little information on what to do to fix: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4317+. ### Proposal Add to the admin view on any given reconciliations a separate "Retry Failed" action or similar that lets support team trigger `RetryDeclinedReconciliationJob` on behalf of the customer without them needing to update their payment method again. ### Workaround It does seem to work if the customer updates their payment method and simply re-enters their CVV (which is cleared on page load). That appears, anyway, to hit `PaymentMethodsController#update`, which then enqueues `RetryDeclinedReconciliationJob` --- **Support Priority Score:** (1, 0, 0, 3, 2, 0, 0, 3, 0, 3, 0) => 12