Skip to content

Scheduled Jobs

Schedules start Agentic Unit jobs automatically from Backoffice using a five-field cron expression and an IANA time zone.

Access

Schedules belong to a team. Team members can view and manage their team's schedules; administrators can manage schedules across teams. The selected agent must be available to the owning team.

The platform applies limits to the number of schedules and their minimum run interval. Backoffice reports a validation error when a schedule exceeds the configured limits.

Create A Schedule

In Backoffice, open Schedules and create a schedule with:

  • A descriptive name and optional description
  • The owning team
  • An enabled agent
  • A prompt that is complete enough to run without an interactive clarification
  • A five-field cron expression
  • An IANA time zone such as Europe/Warsaw
  • A concurrency policy
  • Whether the schedule starts enabled

Use repository names, ticket identifiers, expected outputs, and verification steps in the prompt where applicable. The runtime uses the selected team's permissions and the selected agent's skills.

Concurrency

Choose how Agentic Unit behaves when the previous occurrence is still active:

  • Skip does not start a second overlapping job.
  • Allow starts the new occurrence even when an earlier one is still active, subject to the team's job concurrency limit.

Use Skip for most maintenance and reporting tasks. Use Allow only when each occurrence is independent and overlap is safe.

Operate A Schedule

From Backoffice you can:

  • Enable or pause a schedule
  • Edit its prompt and timing
  • Run it immediately without waiting for the next occurrence
  • Review recent execution information
  • Delete it when it is no longer needed

Repeated failures can cause a schedule to be disabled automatically. Fix the underlying configuration or prompt, then re-enable it.

Time And Cron Guidance

Cron uses five fields: minute, hour, day of month, month, and day of week. The configured IANA time zone controls how those fields are interpreted, including daylight-saving changes.

Before enabling a schedule, verify the next run time shown in Backoffice. Avoid assuming the server's local time or UTC unless that is the time zone you chose.

Safety

Scheduled output requires the same human review as an interactive job. Use branch protection, keep the prompt narrowly scoped, and never embed credentials in a schedule. Required secrets must come from approved secret integrations.