Skip to main content
When a renewal payment fails, Reorder creates a dunning case and begins automatically retrying the payment according to the retry schedule configured in Settings → Subscription Settings. The Dunning queue at /app/subscriptions/dunning gives you a live view of every active and historical dunning case. From here you can inspect the retry history, trigger an immediate retry, override the retry schedule for a specific case, or manually close a case as recovered or unrecovered.

The dunning queue

Navigate to Subscriptions → Dunning to open the queue.

Columns

Click any row to open the detail page for that case. Use the search input to find cases by subscription reference, customer name, product title, variant title, SKU, payment provider, or last payment error code.

Filters and inputs

Click Add filter to filter by Status. Applied status filters appear as chips in the toolbar. The queue also exposes dedicated inputs that let you narrow results further:

Sorting

Use the sorting menu to sort by Status, Next retry, Attempts, or Last attempt.

Dunning case statuses

Dunning case detail

Click a row in the queue to open the detail page. The detail page is split into two columns:
  • Left column — Case overview, payment summary, retry schedule, attempt timeline, and technical metadata
  • Right column — Linked subscription card, linked renewal cycle card, and linked order / payment card (where records exist)

Detail actions

The action menu in the top-right of the detail page provides the following actions: Actions are disabled while a mutation is in progress.

Retrying a payment immediately

Use Retry now to attempt payment recovery without waiting for the next scheduled retry.
1

Open the case detail

Click the dunning case row in the queue to open the detail page.
2

Select Retry now

From the action menu, select Retry now. A confirmation prompt appears.
3

Confirm

Confirm the action. Reorder immediately attempts to charge the payment method.
Retrying now triggers an immediate payment attempt. Make sure the customer’s payment method is in a state that can succeed before proceeding.

Marking a case recovered

Use Mark recovered to manually close a dunning case when payment has been handled outside of the automatic retry flow — for example, after resolving an issue directly with your payment provider.
1

Open the case detail

Click the dunning case row in the queue to open the detail page.
2

Select Mark recovered

From the action menu, select Mark recovered. A confirmation prompt appears.
3

Confirm

Confirm the action. The case is closed as recovered and the linked subscription returns to active.

Marking a case unrecovered

Use Mark unrecovered to close a dunning case when you’ve determined the payment cannot be collected.
1

Open the case detail

Click the dunning case row in the queue to open the detail page.
2

Select Mark unrecovered

From the action menu, select Mark unrecovered. A confirmation prompt appears.
3

Confirm

Confirm the action. The case is closed as unrecovered.

Overriding the retry schedule

Use Edit retry schedule to change the retry intervals or maximum attempts for one specific dunning case without changing the global settings.
1

Open the case detail

Click the dunning case row in the queue to open the detail page.
2

Select Edit retry schedule

From the action menu, select Edit retry schedule. A drawer opens with the current schedule pre-filled.
3

Update the schedule

Adjust the Intervals (in minutes) and Max attempts for this case. The drawer shows a warning if the override creates a risky schedule configuration.
4

Add an optional reason

Enter an optional reason for the override to capture context in the audit trail.
5

Confirm and save

A final confirmation prompt appears before the override is saved.
Retry schedule overrides apply only to the specific dunning case you’re editing. The global retry policy in Settings → Subscription Settings is not affected.