Retry

POST /retry/:id

Retry a failed token launch.

Request

POST /retry/:id

Path Parameters

Parameter	Type	Description
id	string	Follower UUID

Response (Success)

{
  "success": true,
  "message": "Retry initiated",
  "followerId": "abc-123-def"
}

Response (Error)

{
  "error": true,
  "message": "Cannot retry: status is launched, not failed"
}

Error Conditions

Condition	Message
Not found	Follower not found
Not failed	Cannot retry: status is {status}, not failed
Max retries	Max retry attempts (3) exceeded

Example

# Retry a specific follower
curl -X POST http://localhost:3000/retry/abc-123-def

---

Retry Workflow

1

Find failed launches

curl "http://localhost:3000/followers?status=failed" | jq '.followers[] | {id, username, retryCount, errorMessage}'

2

Review error

curl http://localhost:3000/followers/abc-123-def | jq '.follower | {username, errorMessage, retryCount}'

3

Retry launch

curl -X POST http://localhost:3000/retry/abc-123-def

4

Verify success

curl http://localhost:3000/followers/abc-123-def | jq '.follower.status'

# Should be "launched" or "processing"

---

Batch Retry

Using script

pnpm retry-failed

Options:

• --dry-run - Preview without making changes

• --limit=N - Limit number of retries

# Preview
pnpm retry-failed --dry-run

# Retry up to 10
pnpm retry-failed --limit=10

Using API (custom script)

#!/bin/bash

# batch-retry.sh

# Get failed follower IDs
ids=$(curl -s "http://localhost:3000/followers?status=failed&limit=100" | jq -r '.followers[].id')

# Retry each one
for id in $ids; do
  echo "Retrying $id..."
  curl -s -X POST "http://localhost:3000/retry/$id"
  sleep 2  # Rate limit
done

---

Retry Limits

Setting	Default	Description
MAX_RETRY_ATTEMPTS	3	Max retries per follower
RETRY_DELAY_MS	5000	Delay between retries

Exceeded max retries

If retryCount >= MAX_RETRY_ATTEMPTS, the API returns an error:

{
  "error": true,
  "message": "Max retry attempts (3) exceeded"
}

To retry anyway, manually reset the retry count:

UPDATE followers 
SET retry_count = 0, status = 'pending' 
WHERE id = 'abc-123-def';

---

What happens during retry

1

Validation

Check status is failed and retries not exceeded

2

Reset status

Set status to pending, clear error

3

Log action

Record RETRY_SCHEDULED event

4

Process launch

Execute full launch pipeline

5

Update status

Set to launched or failed

flowchart LR
    A[POST /retry/:id] --> B{Valid?}
    B -->|No| C[Return Error]
    B -->|Yes| D[Reset to pending]
    D --> E[Log RETRY_SCHEDULED]
    E --> F[processLaunch]
    F --> G{Success?}
    G -->|Yes| H[Status: launched]
    G -->|No| I[Status: failed]

---

Common retry scenarios

Insufficient funds

Error: Insufficient funds for rent

Fix: Fund deployer wallet, then retry.

# Check balance
solana balance <DEPLOYER_ADDRESS>

# Fund if needed
solana transfer <DEPLOYER_ADDRESS> 1 --from <SOURCE>

# Retry
curl -X POST http://localhost:3000/retry/abc-123-def

Network timeout

Error: Transaction was not confirmed in 30 seconds

Fix: Usually temporary. Just retry.

curl -X POST http://localhost:3000/retry/abc-123-def

IPFS upload failed

Error: IPFS upload failed: 503

Fix: pump.fun API temporarily unavailable. Wait and retry.

sleep 60
curl -X POST http://localhost:3000/retry/abc-123-def

Auth expired

Error: Failed to authenticate with X

Fix: Refresh X cookies, restart engine, then retry.

# Update .env with fresh cookies

# Restart engine
pnpm dev

# Retry
curl -X POST http://localhost:3000/retry/abc-123-def