Preparing your workspace
Preparing your workspace
Recurring outreach should repeat an approved operating process—not create an invisible autopilot. The cadence, next run, controls, and delivery safeguards should remain visible.
Weekly or longer intervals fit many market-refresh workflows. Minute-based recurrence is useful for testing and tightly controlled operations, not a reason to contact the same audience repeatedly.
Be explicit about whether the run discovers a fresh audience, prepares a new sequence, or schedules already-approved jobs. Preserve campaign and delivery identifiers across retries.
At-least-once dispatch means a due event can reappear. Atomically claim each delivery job and store the provider result so repeated dispatch cannot call Resend or Twilio twice.
Show the next run, allow the schedule to pause without deletion, and apply suppression and daily-cap checks on every execution.