---
app: agent
audience:
  - owner
since: 0.1.8
ui_only: false
agent_actions:
  - tool: app_automation_list
    permission: auto
    example: when does the low-stock check run?
agent_examples:
  - can I move the owner briefing to 6 am?
  - why did the briefing say 'ran late'?
llm_weight: demote
title: Schedules
description: When scheduled automations run, why two agents never run the same
  one, and what you can change.
editUrl: true
head: []
template: doc
sidebar:
  order: 4
  hidden: false
  attrs: {}
pagefind: true
draft: false
---

import { AgentAsk } from "@components";

**Who this is for:** an owner wondering when things happen.

## Fixed times, room time zone

Each scheduled automation has a fixed time in the [catalog](/agent/automations/catalog/) — the owner briefing at 07:30, low stock at 07:30 Mon–Sat, overdue invoices at 09:00 Mon–Fri. The time is read in the **time zone of the agent's room** (Settings of the room → **Time zone**), so an office with a Jakarta and a Makassar room briefs each at its own 07:30.

To spread the load, every agent's jobs are shifted by a few minutes per desk (the third agent runs about 14 minutes after the first). The exact next run is on the Automations tab of the agent and in the Activity tab of its room.

## What you can change

- **Which agent owns a job** — switch it off on one agent and on for another. A scheduled job has one owner in the whole office.
- **When its owner leaves** nothing needs doing: removing an agent moves each of its jobs to a colleague doing the same kind of work (a roommate first), and a banner shows where each went. Payroll stays off until you choose who runs it — see [Move or remove an agent](/agent/office/move-or-remove-an-agent/).
- **The daily meeting time** of a room — the room's own setting; see [Daily meetings](/agent/meetings/daily-meetings/).
- **Run now** — the Automations tab of an agent runs any job immediately; the result is delivered like a scheduled one.

Times of catalog jobs themselves are not editable in the app; ask for a different time and we will consider it for the catalog.

A handful of jobs are marked "every working hour" in the catalog (the engineering ticket sync, for one) — these follow the **Working hours** you set on the agent's room instead of a fixed range, so a night-shift Engineering room (`20-05`) runs its hourly sync at night, not during the catalog's default daytime hours. Most jobs are unaffected and keep their fixed catalog time.

## Late and missed runs

A job fires only while its agent is awake and the app is open. The app wakes an agent a few minutes before a job is due; a job missed while the app was closed runs once at the next launch (badge **Ran late** in the Activity tab) if it is less than a day old, older ones are skipped. Details in [Keeping the office running](/agent/automations/always-on/).

## Ask your agent

<AgentAsk />

## Related

[Automation catalog](/agent/automations/catalog/) · [Keeping the office running](/agent/automations/always-on/) · [Rooms](/agent/office/rooms/)