Skip to main content
Time-based triggers run Automations on a schedule: dependency updates, security scans, compliance checks, nightly builds. Use them when the work should happen predictably without someone clicking Run each time.

​
Good fits for scheduled runs

  • nightly validation and cleanup
  • weekly dependency maintenance
  • regular backlog triage
  • periodic reporting or compliance checks

​
Configuration

​
Target scope

  • Projects: select projects. Runs on all repositories within them.
  • Repositories: use a search query (see manual triggers for examples).
Time-based trigger configuration

​
Schedule

FrequencyOptions
HourlyMinute (0-59)
DailyHour, minute
WeeklyDay of week, hour, minute
MonthlyDay of month, hour, minute
Schedule configuration Examples:
  • Weekly dependency updates: Monday at 2 AM
  • Nightly security scans: Daily at 1 AM
  • Monthly compliance: First of month at midnight

​
Timezone

Schedules are evaluated in UTC. Keep that in mind when choosing times for teams that work in other timezones.

​
Scheduling tips

  • Run outside peak working hours when the workflow is resource-intensive.
  • Leave enough time for one run to finish before the next one begins.
  • Start with a narrower target set before scheduling the Automation broadly.
  • Pair scheduled runs with service accounts when you want stable credentials independent of an individual user.

​
After you enable the trigger

Once saved, the Automation waits for the next matching schedule window. Review the first few runs in Execution History to confirm the cadence and targets are correct.

​
Next steps