# Schedules and Runs

- URL: https://betteranalyst.com/docs/data-flows/schedules-and-runs
- Updated: 2026-11-01
- Author: Better Analyst

Schedule Data Flows, run them on demand, review run history, and repair flows that pause or lose access.

Run a saved data flow on demand or add a schedule allowed by your plan. The flow page shows its saved configuration, health, recent runs, and rolling fair-use status.

![Data Flow detail page showing its pipeline, schedule, health, and run history](https://betteranalyst.com/docs/data-flows/schedules-and-runs/flow-detail-page-light.png)

Use the flow page to run now, review history, and repair or resume delivery.

## Schedule Options

| Frequency | Options |
| - | - |
| Hourly | Choose the minute of each hour and a time zone |
| Daily | Choose a time and time zone |
| Weekly | Choose a day of the week, time, and time zone |
| Monthly | Choose a day of the month, time, and time zone |

Pro supports daily, weekly, and monthly schedules. Team and Enterprise also support hourly schedules. On grandfathered plans, Starter supports weekly and monthly schedules, Max adds daily, and Business adds hourly. Scheduled runs start near the selected time but source-system freshness and queueing can add delay.

The selected time zone controls when the schedule runs. Check it when you create or edit the schedule, especially if daylight saving changes affect your reporting time.

![Schedule this flow dialog with cadence, day of week, time, and timezone options](https://betteranalyst.com/docs/data-flows/schedules-and-runs/schedule-modal-light.png)

Add a cadence to a saved flow — the plan decides which frequencies are available.

## Run Now

Select **Run now** from a paid saved flow whenever you need fresh output. Paid plans do not have a separate monthly execution quota. A safety limit of 20 admitted manual starts per rolling hour applies to each flow.

Free does not save Data Flow definitions. Instead, **Run test once** makes a real, atomic Google Sheets delivery. Free includes 10 successful tests per rolling 30 days, drawn against a 50,000-row rolling fair-use allowance. Failed or cancelled attempts do not count, and a successful empty delivery does.

Scheduled runs use the saved source, transform, destination, and write mode. A manual run follows the same saved flow and only changes the trigger.

## Run History

Run history records each attempt, including:

- Rows written
- Duration
- Trigger: **Manual** or **Scheduled**

Use the latest failed row to identify whether the source, transform, or destination needs attention.

## Health and Automatic Pausing

Each flow has a health badge:

| Badge | Meaning |
| - | - |
| Healthy | The flow has access to its source and destination and is not paused |
| Paused | Scheduled delivery is paused |
| Needs reconnect | Access to a required source or destination must be restored |
| Plan incompatible | The destination or cadence is not available on the current plan |
| Over plan limit | The definition is preserved but does not currently occupy an active-flow slot |

A flow pauses automatically after three consecutive failed runs. It pauses immediately when access is lost, including when a source is disconnected, destination permission is removed, or the destination is deleted.

When a flow pauses, Better Analyst sends an email alert. If the flow was created from chat, Better Analyst also posts a message in that chat.

Fair-use pauses recover automatically as usage rolls out of the 30-day window. Plan-incompatible and overflow flows require an explicit configuration change, resume, or **Use plan slot** action so an upgrade never causes an unexpected write.

A flow also stops running when one of its data sources gets [per-member rules](https://betteranalyst.com/docs/teams/per-member-data-access), or tables and columns limited by member. A flow runs without a person and writes where others can read, so it can't use a source that shows each person different rows. Before the rules are saved, the person changing them sees which flows will pause. The flow can run again once the rules are turned off.

## Repair and Resume a Flow

1. Open the flow and review its latest run and health badge.
2. Reconnect the source, restore destination permission, replace a deleted destination, or fix the reported configuration problem.
3. Resume the flow from its page.
4. Select **Run now** to confirm the repair before the next scheduled run.

For Google Sheets destinations, the flow also keeps destination change history to help you review where previous runs were sent. See [Destinations](https://betteranalyst.com/docs/data-flows/destinations).

## Next Steps

- [Create a flow](https://betteranalyst.com/docs/data-flows/create-a-flow)
- [Choose a destination and write mode](https://betteranalyst.com/docs/data-flows/destinations)