Scheduling Tasks
Schedule tasks to run daily, weekly, or monthly. Configure time zones, monitor recent runs, pause schedules, and manage plan limits.
Schedule your tasks to run automatically at regular intervals. Wake up to fresh analysis without lifting a finger.
Schedule Options
Manual Only
Run tasks on demand:
- Select Run when needed
- Best for occasional analysis
- Available on all plans
Daily
Run every day:
- Set specific time
- Good for daily metrics
- Requires a paid plan
Weekly
Run once per week:
- Choose day of week
- Set specific time
- Good for weekly reports
Monthly
Run once per month:
- Choose day of month (1-28)
- Set specific time
- Good for monthly summaries
Monthly schedules use days 1-28 to avoid issues with months of different lengths.
Setting Up a Schedule
New Task
- Create a task with Save as task from a working chat
- Open the task and select Schedule
- Choose the frequency, day, time, and time zone
- Select Schedule to save it
Existing Task
- Open the Agents section's Tasks area
- Select the task
- Select Schedule or Scheduled
- Update the schedule settings and save
Delivering Results
Choose who gets the results and how:
- Who should receive the results? On team tasks, pick teammates. If you pick nobody, only you receive them.
- Email: results arrive by email.
- Slack DM: results arrive as a Slack direct message. People who haven't connected Slack get an email instead.
- Also post to a Slack channel: post each run to a channel Better Analyst has been added to.
Pick at least one. Slack delivery needs a team task and a connected Slack workspace; see Send scheduled reports to Slack.
Private Projects
A task in a private project sends results only to people who can see the project, and can't post to a Slack channel. Direct messages still work.
Time Zones
Choose the time zone for the task in its scheduling dialog. The selected time zone controls when that schedule runs.
Confirm the task's time zone to ensure it runs when expected.
Schedule Best Practices
Choose the Right Time
- Daily reports: Early morning (6-8 AM)
- Weekly summaries: Monday morning
- Monthly reports: 1st or last business day
Allow for Data Updates
If your data source updates at specific times:
- Schedule tasks after data refreshes
- Leave buffer time for processing
- Account for time zone differences
Stagger Multiple Tasks
If you have several scheduled tasks:
- Space them apart by 30+ minutes
- Prioritize critical reports earlier
- Avoid scheduling all at the same time
Monitoring Scheduled Runs
Run History
View past executions in Recent runs on the task page. Each entry shows its status, time, and where the results were delivered (for example, Emailed 2 · Slack DM 1 · Posted to channel), and successful runs link to the resulting chat.
Run Status
| Status | Meaning |
|---|---|
| Success | Completed without errors |
| Failed | Error occurred |
| Running | Currently executing |
| Skipped | Didn't run (e.g., data unavailable) |
Error Notifications
When a scheduled run fails:
- Error logged in run history
- Details available for troubleshooting
- The task owner is told by Slack DM if their Slack account is connected, otherwise by email
- Email recipients get a failure email when email delivery is on
- A Slack channel the task posts to gets a short notice
Managing Schedules
Pause a Schedule
Temporarily stop scheduled runs:
- Open the task
- Open the scheduling dialog
- Select Pause task
- Schedule it again when ready
Change Frequency
Update how often it runs:
- Open the task
- Open the scheduling dialog
- Select a new frequency
- Save changes
Delete Schedule
Remove automation but keep the task by opening its scheduling dialog and selecting Pause task.
Data Sources That Filter Rows per Member
Scheduled tasks run without a person, so they can't use a team data source that shows each person different rows. That's a source with per-member rules, or with tables and columns limited by member.
- If you create or schedule a task that uses one, it's refused with a message like: "Scheduled tasks can't use Sales DB yet, because it shows each person different rows."
- If a data source gets per-member rules after a task was scheduled, the task's schedule is turned off. Before saving, the person changing the rules sees which tasks will pause.
- If the rules are turned off later, the task stays unscheduled. Its owner can schedule it again.
To keep a scheduled report, remove the per-member source from the task, or use a data source without per-member rules.
Schedule Limits by Plan
| Plan | Scheduled Tasks | Frequencies |
|---|---|---|
| Free | 0 (3 saved tasks, run manually) | — |
| Pro | Unlimited | Daily, Weekly, Monthly |
| Team | Unlimited | Daily, Weekly, Monthly |
| Enterprise | Unlimited | Daily, Weekly, Monthly |
Troubleshooting
Task Didn't Run
- Check schedule is enabled (not paused)
- Check whether one of its data sources now has per-member rules
- Verify time zone settings
- Review run history for errors
- Confirm plan supports scheduling
Wrong Time
- Check account time zone setting
- Verify schedule configuration
- Account for daylight saving changes
Missed Runs
- Tasks don't "catch up" on missed runs
- If the system was unavailable, run skips
- Manually run to get latest results