Pipeline and scheduled tasks

The Pipeline page is where everything that runs on a clock is watched. It draws your syncs, the tasks that rebuild your models after them, the search indexes that refresh, and the report deliveries that go out, on one page, so you can see what runs, what it depends on, and when it reaches your team.

Go to Monitor · Pipeline. Every member can read it. Owners and admins can also change when things run from here. Press Refresh at the top right to reload it.

The four stages

The Your pipeline panel lays the work out in the order data moves.

The panel's subtitle counts them, for example 2 sources · 2 tasks · 4 indexes · 2 deliveries. The Sync, Transform and Deliver stages list six items at a time, with arrows to page through. Sync and Transform also have a +, which opens Connections or the Tasks tab.

Each row shows a coloured dot, the name, its state and when it runs. A red dot means the last run failed, or a task is suspended. Amber means paused. Green is fine.

To find something, type in Find a connection, task or delivery…. The status menu offers All statuses, Needs attention (failed or suspended), Active and Paused.

Selected flow

Select a connection, task or delivery and press Selected flow to draw just that item with its direct dependencies: the sync a task waits for, the tables it refreshes. Back to all returns to the overview. The button is disabled until you select one of those.

The inspector

Selecting an item opens an inspector beside the panel.

Members who are not owners or admins see Only owners and admins can change when this runs.

The account schedule

Under the overview, Account schedule shows syncs, tasks, model runs, index builds and deliveries on one clock, one day at a time.

Read a lane like this:

• Bars are recorded runs, coloured by outcome. A bar starts when the run started and ends when it finished.
• Diamonds are future starts, worked out from the current schedule. They appear for today and days to come.
• Circles are runs that wait for a sync to finish. Their exact start time is not known, because it depends on how long the sync takes.
• The dashed line is now.

Model runs are builds, procedure calls and maintenance statements that ran outside a task. Index builds are sanda search refreshes.

You can move around:

• Calendar day shows 00:00 to 24:00. Next 24 hours shows the day ahead from now. Use Previous day, Next day, the date box and Today to move.
• The timezone menu chooses between your browser's timezone and UTC. A day on which the clocks change has 23 or 25 hours, and the header says so.
• Find an action… and the type menu (All actions, Syncs, Tasks, Model runs, Index builds, Deliveries) filter the lanes.
• Timeline shows the lanes. In time order lists the same events as an agenda, each tagged Recorded, Scheduled or After sync. Select a bar to open its lane in the agenda.
• If more than 2,000 runs were recorded in the window, Load more recorded activity fetches the rest. All scheduled starts are always shown.

The 15 minute grid

sanda's scheduler wakes every 15 minutes, on :00, :15, :30 and :45, and everything scheduled is held to that grid: tasks, connection syncs, search index refreshes and report deliveries. A schedule can only name one of those minutes, and the time pickers only offer them. A start set for 9:07 would run at 9:15.

The same wait applies to anything you queue by hand. Run now on a task queues a run, and it starts at the next quarter hour.

A run also has a ceiling, because it has to fit inside one tick: no task runs for longer than 14 minutes.

Find what failed

1. Set the status menu to Needs attention. It shows anything whose last run failed, and anything suspended.
2. Select the item. The inspector shows its last outcome, and for a task the state.
3. Open the item to read the error. A task's runs list the error on the run and on each step. For a connection, see Monitor syncs. For a delivery, see Delivery.

A task that fails several times in a row pauses itself and shows suspended. Fix the cause, then press Resume. See When a task fails.

Failures are also emailed to your alert recipients, once a day for each task or delivery, if you have that switched on in Settings · Plan & budget · Budget & alerts.

When the workspace is suspended for its budget, scheduled work is held. Nothing is queued, and once the workspace is resumed each item carries on from its next slot, without replaying what it missed.