Auto Schedules

Viewing captures

Everything one schedule has produced, in one place — with the tools to keep what matters and clear out what does not.

Opening a schedule

Click a schedule in the Auto Schedules list, or choose View from its menu. The header repeats what the list showed — status, country, URL, how often, next run and the capture counters — and adds:

A Pause switch. Pausing only stops new captures.
Edit schedule, which opens the schedule form.
Trigger API, which copies the address that fires this schedule from your own code. See the Auto Schedule API.

A sitemap schedule also has a Sitemap runs panel listing each run, how many of its pages were captured, and why a run captured nothing. See Sitemap schedules.

What each capture shows

Below the header, Captures lists every capture, newest first, as a card with its thumbnail.

Value	Meaning
`Origin`	Quick for a capture somebody started with Quick Capture, Quick API for one fired through the Auto Schedule API. A scheduled capture says nothing extra. The pipeline is identical in all three cases.
`Failed`	A capture that produced nothing says “Capture failed”, or “Failed · page returned 503” with the page’s status. It is not counted against your plan — except a capture the website refused, which is free up to 5% of your plan’s monthly captures and counted after that. A page that answered 400 or above but still rendered is kept and says, for example, “Page returned 404 · Kept until …”; it counts like any capture.
`Changed 12%`	Shown when change detection found the page different from its previous capture.
`Tags`	Inherited from the schedule.
`Retention`	“Kept until deleted”, or “Not kept after delivery” for a deliver-only capture.
`Favourite`	A heart toggle. See below.

Each card’s menu offers View, Download and Delete.

The capture viewer

Opening a capture shows it full size in a side panel, with Capture Details beside it:

URL
Location — the country it was captured from
Resolution, format and file size
Response — the HTTP status the page answered with
Kept until
Page source, when the profile saves it
Tags
Changes — whether the page changed since the previous capture, and by how much

When change detection compared the capture, the viewer has three tabs: Capture, What changed (the capture with the changed parts tinted red) and Before / after (the previous capture and this one, with a handle to slide between them).

This is your diagnostic panel

A blank-looking capture with a 200 status and a plausible file size usually means the page needed longer — raise the page timeout. A 403 or 404 means you never reached the page at all, and no capture setting will fix it.

Links from emails land here

A capture email opens this page with that capture selected. If it is not on the page — on a later page, or removed by retention — the page says so rather than quietly showing you a different one.

Download a month

Download a month lists the months this schedule has kept captures for. Pick one, tick Include the page source if you want it, and press Prepare download. You get a link to one archive of that month.

Files are named by capture time, in the schedule’s own time zone.
The archive is built as it downloads, so it cannot be paused or resumed — if the connection drops it starts again.
Captures set to Do not keep after delivery went to your own cloud storage and are not in the archive.

Retention and deletion by range

Beside Download a month are three actions: Retention, Keep a range and Delete (on a phone, under Manage).

These apply to a date range, not to a selection

You do not tick captures. Each action opens a panel where you set Captured from and Captured to (or Keep from and Keep to), and it applies to every capture of this page in that range. Leave a date empty to leave that end open. A preview tells you what will be affected before you confirm.

Value	Meaning
`Retention`	Sets how long the captures in the range are kept. Shortening is always allowed; extending needs a running plan. Do not keep after delivery cannot be applied to captures that already exist — delete them instead.
`Keep a range`	The inverse — everything outside the dates you give is removed. Powerful, and the one to be most careful with.
`Delete`	Removes every capture in the range, permanently.

Every panel has an Include favorites checkbox. It is off by default, so favourites are skipped unless you deliberately tick it.

Favourites

The heart on a capture marks it as one to keep. It is not decoration — favourites are excluded from bulk deletion and bulk retention changes unless you explicitly include them.

Favourite the capture that shows the thing you will need to point at later.
Favourite before a clear-out, not after. The protection only helps if it is set when the bulk action runs.
Favouriting protects against the bulk tools. It does not stop a single capture being deleted from its own menu, or the schedule being deleted with its captures.

For anything genuinely important, keep a copy

Favourites protect a capture from a bulk action inside this account. A file you may need in a year — for a dispute, an audit, a claim — belongs in your own storage as well. Cloud delivery does that automatically.

Did this page answer your question?

Tell us what is missing