6. Trigger Validation Retry

Purpose: Re-enqueue facts that have been stuck in pending validation for 4+ hours so they get another validation attempt.

Prerequisites:

  • Web app running locally (bun run dev:web)
  • Validation worker running (see Start Workers)
  • CRON_SECRET set in .env.local

Cost / Duration: ~$1 AI cost | ~2 minutes

Prompt

Trigger a validation retry for facts stuck in pending_validation status.
This finds facts that have been waiting for validation for 4+ hours and
re-enqueues VALIDATE_FACT messages for them.

Make sure the web app and validation worker are running, then hit the
validation retry cron endpoint:

```bash
curl -X POST http://localhost:3000/api/cron/validation-retry \
  -H "Authorization: Bearer $CRON_SECRET"
```

After triggering, verify that messages were enqueued:
```bash
bun scripts/diagnose-pipeline.ts
```

The VALIDATE_FACT queue should show new messages. After processing,
previously stuck facts should move to validated or rejected status.

If no facts are re-enqueued, there may not be any facts stuck for 4+ hours.
Check the database for pending_validation facts with recent timestamps.
If facts fail validation again, investigate the specific error in worker logs.

Verification

  • Validation retry endpoint returns success (HTTP 200)
  • VALIDATE_FACT queue shows new messages
  • Previously stuck facts move to validated or rejected status after processing
  • No new stuck facts accumulate

Back to index