Dunning

When a subscription billing attempt fails, Gro’s dunning system automatically retries the charge on a configurable schedule. This helps you recover revenue that would otherwise be lost to expired cards, insufficient funds, or temporary payment issues.

How It Works

1. A subscription billing attempt fails
2. Gro creates a dunning episode — a record that tracks the retry journey
3. Automatic retries are scheduled based on your configured intervals
4. If a retry succeeds, the episode is marked as recovered
5. If all retries are exhausted, Gro applies a final action (pause, cancel, or keep active)

Episode Statuses

Status	Meaning
Ongoing	Active dunning — retries in progress
Recovered	Payment succeeded after retries
Lost	All retries exhausted — revenue not recovered

Configuration

Navigate to Subscriptions → Settings → Dunning in the Gro dashboard:

Retry Schedule

Define when retries happen after the initial failure. For example:

• Retry 1: 3 days after failure
• Retry 2: 5 days after retry 1
• Retry 3: 7 days after retry 2

Final Action

Choose what happens when all retries are exhausted:

Action	Description
Pause	Subscription is paused — can be resumed when payment is updated
Cancel	Subscription is cancelled — can be reactivated via winback
Keep active	Subscription stays active — billing will be attempted again on the next cycle

Events

Dunning episodes generate events you can use in email flows:

• dunning:started — first failure, dunning begins
• dunning:recovered — payment succeeded after retries
• dunning:lost — all retries exhausted

Use these events in Gro Flows or Klaviyo to send payment failure notifications and payment update reminders to customers.