> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/schedules.md). # Schedules Create recurring or cron-based schedules that start Agent runs in a project. Control → **Schedules** manages scheduled **Agent work** in the current Project. These are not Workflow schedules. If you need a recurring Workflow trigger, use Scheduling workflows under **Build and improve → Automate**. ![Create an Agent schedule with task or heartbeat kind, recurring or one-off cadence, timezone, session behaviour and prompt.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fgit-blob-690df986bb2b97dfd5f6cb76f15032ec73355319%2Fcontrol-schedules-create.png?alt=media) ### What you can schedule The current form supports: * **Kind** — `Task` or `Heartbeat`. A Project can have at most one Heartbeat. * **Cadence** — recurring cron or one-off. * **Cron expression** — recurring schedules default to `0 9 * * *`. * **Time zone** — initialised from the browser's IANA timezone, for example `Europe/Amsterdam`. * **Session** — start a new session or reuse a session. * **Description** — an administrative note about the schedule. * **Prompt** — the instruction sent to the Agent when the schedule fires. The populated list shows each schedule's kind, cadence and timezone, status, last run and next run, with controls to edit, pause or delete it. There is currently **no Run now control**, so testing a schedule means waiting for its next scheduled fire. ### Access and navigation Creating, changing, pausing and deleting schedules requires Builder-level Project access. The underlying read surface is Project-member scoped, but Operators do not see the Control section in the current navigation. Schedules is also an exception to the normal Control tab strip: it is available from the **Control sidebar item** but is not currently present in the horizontal Control tabs. Use the sidebar or the direct Schedules page rather than looking for a Schedules tab. ### Before relying on a schedule Check the timezone, the Project the Agent will run in, and whether the Agent has the Skills, Connections and maintained context needed to do the work without an operator driving the session. A scheduled Agent run changes **when** the work starts. It does not by itself turn an ambiguous foreground task into a well-defined autonomous process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lleverage.ai/administer-and-govern/control/schedules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.