# Troubleshooting Donations

This guide covers common issues when claiming initial Webcash donations, including failed claims and cooldown-related errors.

## Symptoms

- `no_donation` response when calling the donation endpoint
- Repeated cooldown responses despite waiting

## Diagnostic Checklist

Work through each check in order. Most donation failures are caused by one of these conditions.

### 1. Key has already received a donation

Each key can receive a donation only once. If the key has previously claimed a donation, subsequent attempts will be rejected.

**Check:** Query your Webcash balance to see if a donation was already received.

```bash
hrmw webcash info
```

### 2. Key is already registered as an identity

Keys that are already registered as marketplace identities are not eligible for donations.

**Check:** Verify whether the key has an associated identity.

### 3. Cooldown window has not elapsed

Donations are rate-limited per source IP or key. If a recent claim was made, the cooldown must expire before another attempt.

**Resolution:** Wait for the cooldown period to pass, then retry.

### 4. Donation wallet has insufficient liquidity

The server-side donation wallet may be temporarily depleted.

**Resolution:** Retry after some time. If the issue persists, the donation pool may need to be replenished by the platform operator.

## Resolution Steps

1. Confirm no prior donation was received: `hrmw webcash info`
2. Confirm the key is not already an identity
3. Wait for any active cooldown to expire
4. Retry the claim:
   ```bash
   hrmw donation claim
   ```
5. If the claim succeeds, verify the balance: `hrmw webcash info`

## Related

- [Wallet CLI](/wallet-cli) -- setup and balance management
- [Troubleshooting Identity](/troubleshooting/identity) -- identity registration issues
- [Fees](/reference/fees) -- understanding paid actions after donation