Sequences
Resume Subscribers in a Sequence
Continue paused contacts from the sequence step they were paused on
POST
Resume Subscribers in a Sequence
Continue contacts you paused with pause subscribers. Each enrollment goes back to the status it had, on the step it was paused on. Nothing restarts and no step is skipped.
Waits keep their original wall-clock time, the same as when a whole sequence is disabled and enabled again:
Send
- A wait that ran out while the contact was paused continues right away, so the next email can go out as soon as a worker picks it up.
- A wait that has not run out yet still ends when it would have.
not_paused and left alone, so resuming twice is safe.
If the sequence itself is disabled, the enrollments are still resumed, sequenceRunning is false, and the contacts continue once you enable the sequence.
Request
string
required
Sequence ID.
array
Subscriber IDs to resume.
array
Subscriber email addresses to resume, matched case-insensitively.
subscriberIds, emails, or both. Up to 500 targets combined per request.
Response fields
number
Enrollments resumed by this request.
number
Enrollments of the targeted contacts that were not paused.
boolean
false when the sequence is disabled or not live.number
Resumed enrollments handed to the sending queue.
0 while the sequence is
not running.array
Resumed enrollments whose queue handoff failed. They stay resumed and the
stuck-enrollment sweeper picks them up, so you do not need to retry.
array
Every enrollment of the targeted contacts in this sequence with its status
after the request,
waitUntil, and outcome (resumed or not_paused).notEnrolled and notFound work the same as in pause subscribers.