Operations
Batching & Upload
Batch creation, Bison upload, and what uploaded means vs monthly target
What This Does
Batching is the fourth stage — it groups verified contacts into upload-ready batches. Upload is the fifth and final stage — it pushes batches to Email Bison for campaign delivery.
How It Works
Batching
- Verified contacts are grouped into batches (typically by workspace + month)
- Batches are stored in the
contact_batchestable with statusready - Each batch contains metadata: workspace, month, contact count
Upload
- Ready batches are picked up by the
email_bisonqueue - Contacts are pushed to the Bison API as leads
- On success, batch status changes to
uploaded - The Bison API URL is always
send.maverickmarketingllc.com
Monthly Target
The monthly_contact_target measures contacts uploaded to Bison — not raw scraped contacts. Use pipeline_stats_cache.uploaded for progress tracking, not raw_contacts count.
How To Use It
Viewing Batches
- Go to Contacts → Batches tab
- See all batches with status, contact count, created date
- Upload status shows:
ready,uploading,uploaded,failed
Manual Upload Retry
If a batch fails to upload, it stays in failed status. The system will not auto-retry. To retry:
- Check the failure reason in Status Page → Logs →
celery-email-bison - If the issue is resolved (Bison API was down, credentials fixed), the batch can be re-queued from the Contacts page
Common Issues
| Symptom | Cause | Fix |
|---|---|---|
Batch stuck at ready | email_bison queue worker not running | Check Status Page → Celery Workers → email_bison queue depth. Restart worker if needed |
| Upload failed with auth error | Bison API token expired | Go to Settings → Bison Tokens, refresh the token for the workspace |
| Uploaded count doesn't match target | Target counts uploaded contacts, some may have been filtered/rejected by Bison | Check Bison campaign dashboard for rejection reasons |
| Duplicate uploads | Batch re-queued while original was in progress | Bison deduplicates by email — no harm done, but check batch statuses |
Related Alerts
- BisonAPIHighErrorRate: Bison returning >10% errors
- BisonAPIDown: Bison returning >75% errors — API likely down
- EmailEventsQueueDepthHigh: email_events queue >200 (webhook processing backlog)