One job, many row outcomes
An export run is a first-class job: it validates the integration and workspace, enforces the launch gate fail-closed, creates a per-inbox record for every row, and then processes uploads asynchronously. A single failed row does not silently sink the batch — each row carries its own status and failure type.
- Launch-gate pauses and hard stops block job creation and remaining batches.
- Rows blocked for readiness never reach Instantly and keep an actionable, redacted reason.
- Provider failures are classified by type — credential, provider, or internal — for triage.
Retries respect the provider
Transient provider errors retry with exponential backoff, while authentication and validation failures are non-retryable so invalid keys fail fast. Batches are spaced out to avoid tripping provider rate limits during large uploads.
Export completion is not campaign readiness
Instantly accepting an account row means the upload worked. It says nothing about placement, safe volume, or reply performance. Keep first prospect traffic behind launch-gate and seed-placement evidence rather than treating a green export job as approval.