## TL;DR

Set send_at to the unix timestamp of the desired send time, within 72 hours. Reschedule by creating a new batch with corrected content; never reuse a cancelled batch_id.

## Steps

1. Goal: scheduled campaigns you can still stop.

2. Step 1. Generate a batch_id when building the campaign and include it on every message in the batch.

3. Step 2. Set send_at to the unix timestamp of the desired send time, within 72 hours. Per-recipient timing differences go in personalization-level send_at, which overrides the message value.

4. Step 3. Confirm the batch: list the scheduled batch and sanity-check count and timing before the send time.

5. Step 4. If a mistake is found, cancel the batch by its batch_id. Cancellation only works before the send time; after delivery starts it is too late.

6. Verify: a test batch schedules, appears in the batch list, cancels cleanly, and produces no delivered events. Pitfall: scheduling more than 72 hours out is rejected; long campaigns need rolling batches.

## When to use

You are seeing this: Goal: scheduled campaigns you can still stop. Use this skill when you run into "SendGrid scheduled sends and batch cancellation".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
