Skip to main content
Scheduled Sessions let you create recurring Devin sessions that run automatically at the frequency you choose. Use them to automate repetitive tasks like daily reports, periodic code maintenance, routine data analysis, and more.

Creating a Scheduled Session

There are two ways to create a scheduled session:

From the input box

  1. Type your prompt in the Devin input box
  2. Click the three-dot menu (⋯) on the right side of the input box
  3. Select Schedule Devin
  4. You’ll be taken to the schedule creation page with your prompt pre-filled

From the Schedules settings page

  1. Navigate to Settings > Schedules in the sidebar
  2. Click Create schedule
  3. Fill in the schedule details

Configuring a Schedule

When creating or editing a schedule, you can configure the following options:

Name

Give your schedule a descriptive name so you can easily identify it in the list (e.g., “Daily CI Report” or “Weekly Dependency Updates”).

Agent

Choose which agent type should run the scheduled session:
  • Devin — Standard AI software engineer (default)
  • Data Analyst — Optimized for data analysis and queries
  • Advanced — For playbooks and session analysis

Playbook (optional)

Attach a playbook to the scheduled session. The playbook will be applied every time the schedule runs, ensuring consistent behavior across executions.

Frequency

Set how often the schedule should run. The frequency editor supports two modes: Visual mode provides preset options:
  • Hourly — Run every N hours
  • Daily — Run at a specific time every day
  • Weekly — Run at a specific time on selected days of the week
Times are displayed in your local timezone but stored as UTC internally. The editor handles the conversion automatically.
Custom mode lets you enter a standard cron expression directly (e.g., 0 9 * * 1-5 for weekdays at 9 AM UTC). This gives you full flexibility for complex schedules.

Email notifications

Control when you receive email notifications about scheduled session runs:
  • Always — Get notified after every run
  • On failure only — Only get notified when a scheduled session fails (default)
  • Never — No notifications

Prompt

Write the instructions that Devin will follow each time the schedule runs. This is the same as the prompt you would type when starting a regular Devin session.

Managing Schedules

Navigate to Settings > Schedules to see all your scheduled sessions. The list shows each schedule’s name, frequency, last run time, and status.

Status

Each schedule has one of three statuses:
  • Active — The schedule is enabled and will run at its next scheduled time
  • Paused — The schedule is disabled and will not run until re-enabled
  • Error — The schedule encountered consecutive failures

Editing a schedule

Click on any schedule in the list to view its details. Click Edit to modify its configuration, including the name, prompt, agent, playbook, frequency, notification settings, and whether it is enabled or paused.

Pausing and resuming

You can pause a schedule by editing it and toggling the Status switch to Paused. Paused schedules will not create new sessions until re-enabled. Toggle it back to Active to resume.

Deleting a schedule

Click the three-dot menu on a schedule’s detail page and select Delete. This permanently removes the schedule. Past sessions created by the schedule are not affected.

Viewing Past Sessions

Each schedule detail page has a Past Sessions tab that lists all Devin sessions created by that schedule. Click on any session to navigate to its full session view. This is useful for reviewing outcomes, debugging failures, or auditing what the schedule has been doing over time.

Use Cases

Here are some common ways to use Scheduled Sessions:
  • Daily standup reports — Summarize recent PRs, issues, or commits every morning
  • Periodic dependency updates — Check for and apply dependency updates on a weekly basis
  • Recurring data analysis — Generate reports or dashboards from your data at regular intervals
  • Routine code maintenance — Run lint fixes, dead code removal, or test coverage checks on a schedule
  • Monitoring and alerting — Periodically check system health or review logs for anomalies