> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reorderjs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Renewals
> Use the Renewals queue to monitor scheduled and failed billing cycles, review pending plan changes, approve or reject them, and force renewals when needed.
The Renewals queue at `/app/subscriptions/renewals` gives you a real-time view of every billing cycle Reorder has scheduled or attempted. You can see which cycles are waiting to run, which have failed, and which are blocked on a pending plan-change approval. From the queue you can click into any cycle's detail page to review the full attempt history, approve or reject a pending change, or force the cycle to run immediately.
## The renewals queue
Navigate to **Subscriptions → Renewals** to open the queue.
### Columns
| Column | What it shows |
| ---------------- | ------------------------------------------------------- |
| **Scheduled** | The date and time the renewal cycle is due to run |
| **Subscription** | The linked subscription reference and customer |
| **Status** | Current execution state of the cycle |
| **Approval** | Whether this cycle is waiting on a plan-change approval |
| **Last attempt** | When the most recent execution attempt ran |
Click any row to open the detail page for that cycle.
### Search
Use the search input to find cycles by subscription reference, customer name, product title, variant title, or SKU.
### Filters and date range
Click **Add filter** to filter by **Status**, **Approval**, or **Last attempt**. Active filters appear as chips in the toolbar.
The queue also exposes **Scheduled from** and **Scheduled to** date inputs that default to a ±30-day window around today. Adjust these inputs to widen or narrow the visible date range. These date inputs are not shown as filter chips.
### Sorting
Use the sorting menu to sort by **Scheduled**, **Subscription**, **Status**, **Approval**, or **Last attempt**.
## Renewal cycle statuses
| Status | What it means |
| ------------ | -------------------------------------------------------------------------- |
| `scheduled` | The cycle is queued and will run at the scheduled time |
| `processing` | The cycle is currently executing |
| `succeeded` | The renewal completed successfully and an order was created |
| `failed` | The execution attempt failed; the cycle may be retried or moved to dunning |
| `skipped` | The cycle was skipped because the subscription had skip-next-cycle enabled |
## Approval statuses
| Approval status | What it means |
| --------------- | ----------------------------------------------------------------------- |
| `not_required` | No approval is needed for this cycle |
| `pending` | A pending plan change requires operator approval before the cycle runs |
| `approved` | The pending change was approved and the cycle will apply it |
| `rejected` | The pending change was rejected; the cycle will run without applying it |
Whether approval is required depends on the **Renewal behavior** setting in **Settings → Subscription Settings**. When set to **Require review for pending changes**, any cycle that includes a pending plan change will wait for operator approval.
## Renewal cycle detail
Click a row in the queue to open the detail page. The detail page is split into two columns:
* **Left column** — Cycle overview, approval summary, pending changes, attempt history, and technical metadata
* **Right column** — Linked subscription card and generated order card (when the cycle produced an order)
### Detail actions
The action menu in the top-right of the detail page provides the following actions:
| Action | When it's available |
| ------------------- | ----------------------------------------------------- |
| **Force renewal** | Cycle status is `scheduled` or `failed` |
| **Approve changes** | Approval is required and approval status is `pending` |
| **Reject changes** | Approval is required and approval status is `pending` |
Actions are disabled while a mutation is in progress.
## Approving a pending plan change
When a renewal cycle is blocked on a pending plan change, you can approve it to let the cycle apply the change.
Click the renewal cycle row in the queue to open the detail page.
From the action menu, select **Approve changes**. A drawer opens showing the pending change details.
Enter an optional reason for your approval decision.
Submit the drawer. A confirmation prompt appears before the change is saved.
## Rejecting a pending plan change
If you want the renewal to run without applying the pending change, reject it instead.
Click the renewal cycle row in the queue to open the detail page.
From the action menu, select **Reject changes**. A drawer opens.
A reason is required before you can submit a rejection.
Submit the drawer. A confirmation prompt appears before the rejection is saved.
## Forcing a renewal
Use **Force renewal** to manually trigger execution of a cycle that is scheduled or has previously failed.
Click the renewal cycle row in the queue to open the detail page.
From the action menu, select **Force renewal**. A confirmation prompt appears.
Confirm the action. Reorder immediately attempts to execute the cycle.
Forcing a renewal triggers an immediate payment attempt and order creation. Confirm that the subscription and payment details are correct before proceeding.