Auto Schedules

Run, pause and stop

Five actions in the row menu, two of which cannot be undone. This page is mostly about telling those two apart from the three that can.

Quick Capture

Runs one capture immediately, outside the schedule. It uses the same URL, the same Web Profile and the same delivery settings — the only difference is that nobody waited for the cadence to come round.

The row’s status reads Quick Capturing while it runs.
The action is unavailable while a quick capture is already in flight for that schedule.
It does not move the schedule. The next scheduled run stays exactly where it was.
The result is labelled QUICK CAPTURE in the capture viewer, so you can tell it apart from the automatic ones later. A capture fired through the Auto Schedule API reads QUICK CAPTURE API.
A Trigger Window on the profile does not hold it back.

This is the setup loop

After creating a schedule, or after changing a selector or a profile setting, Quick Capture and then look at the result. It is far quicker than waiting a day to discover the page renders wrongly.

It counts against your plan

A quick capture is a capture. On an account close to its included volume, a habit of pressing it repeatedly adds up like any other run.

Pause and resume

Pause stops new captures being taken. Everything already captured stays exactly where it is, and the schedule keeps all its settings.

Value	Meaning
`Status becomes`	Paused.
`Next Run shows`	“No upcoming runs”.
`Existing captures`	Untouched, and still browsable.
`Retention`	Keeps running — pausing does not preserve captures that were due to expire.
`To undo`	Resume, from the same menu.

Pause is the right answer more often than Stop

Site under maintenance, a redesign in progress, a page temporarily behind a login — all of these are pauses. Reach for Stop only when the schedule is genuinely finished.

We pause schedules for you in two cases, and say so on the badge: Paused - storage full when the account has run out of storage, and Paused - subscription ended when the subscription has ended. Both resume on their own once you free up space, add storage or subscribe again.

Stop

Stop ends the schedule permanently. Its status becomes Stopped, no further captures are taken, and it cannot simply be resumed the way a paused schedule can.

A schedule also stops on its own when it passes the Stop after time you gave it, which is the tidier way to plan a finish in advance.

Stop is not reversible from the row menu

If you need the schedule back afterwards, clone it — the clone carries every setting across, and the original’s captures remain where they are.

Clone

Copies a schedule’s settings into a new one, opened for you to adjust before you press Create copy. It is the fastest way to make a near-identical schedule, and the standard way to bring back a stopped one.

Same cadence, tags, profile and page tweaks as the original. The pages and the start and stop times are yours to set: give the copy its own URLs and decide when it should start.
A clone of a sitemap schedule is a sitemap schedule.
Captures are not copied. The clone starts empty, and the original is not touched.

Delete

Removes the schedule and the captures it took. You are asked to confirm first, because this is the one action with nothing to fall back on.

Deleting is not the same as stopping

Stop keeps the schedule and everything it captured, and simply stops adding to it. Delete removes the schedule and its captures. If the captures are a record you may need, stop the schedule and leave it alone — or download them first.

Did this page answer your question?

Tell us what is missing