> For the complete documentation index, see [llms.txt](https://docs.sola.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sola.security/workspace/routines.md).
# Routines
Routines are scheduled [agent](/workspace/agents.md) runs that execute automatically.
Configure one with a set of instructions, an agent, a schedule, and a project scope, and Sola handles the rest. Every run is logged and auditable, and you can continue investigating in chat.
Sola Agent Routines
{% hint style="info" %}
Routines are [available on paid plans](https://sola.security/pricing/).
{% endhint %}
{% embed url="" %}
## Creating routines
A routine ties together an [**agent**](/workspace/agents.md), a **task**, a **schedule**, and a **project scope**. Once created, it runs on its own at the configured frequency.
Creating and managing routines requires Owner or Admin access. Contributors can view run history for projects they have access to.
**To set up a routine, complete the following:**
* **Name** - Enter a short, descriptive name for the routine.
* **Task** - Write a clear, self-contained prompt describing what the agent should do on each run, up to 1000 characters.
* **Agent** - Select the agent to run the routine. If your workspace has no custom agents, the Sola default agent is selected automatically; if it does, the default agent still appears as an option alongside them. The agent's instructions, tools, and skills apply to every run.
* **Project** - Assign the routine to an existing project, start a new one, or create one from a template.
* **Schedule** - Set how often the routine runs: every hour, day, week, or month, with a specific day, date, or time where relevant.
## Reviewing run history
Every run is logged, showing exactly what the agent did, what it found, and what it produced.
**To review a routine's run history**, go to ***Routines*** and open the routine.
The routine's overview shows its schedule, assigned agent, project, and current status: **Active**, **Paused**, or **In progress**. Below that, run history lists every past run, each with its own status: **completed**, **In progress**, or **Failed**.
Open any run to see the run details and output.
To continue investigating a run, click **Continue in chat** to open it in a new chat session grounded in that run's context.
## Managing routines
The Routines page gives you a workspace-wide view of all your routines.
From this page you can:
* See all routines at a glance, with last run time and status.
* Enable or disable any routine.
* Filter by status, agent, or project.
* Add new routines.
## Routines and workflows
**Automate work with routines**. Routines and workflows are both ways to automate work, but they work differently.
**Routines** run an agent on a schedule. The agent reasons over the task, uses its tools, and decides how to proceed. Use routines for recurring investigations or monitoring tasks where the path to the answer may vary.
**Workflows** execute a fixed sequence of predefined steps in order. Use workflows for repeatable, structured processes where each step is known in advance.
***
## FAQs
### How are routines different from agents?
A routine is a saved configuration that runs an agent automatically, on a schedule. An agent is the actor: it has its own instructions, tools, and memory, and reasons over the task it's given. You can invoke an agent directly in chat with @mention, or let a routine invoke it for you on a recurring basis.
### How are routines different from workflows?
Routines run an agent on a schedule. The agent reasons over the task, uses its tools, and decides how to proceed. Workflows execute a fixed sequence of predefined steps in order. Use routines for recurring investigations where the path to the answer may vary; use workflows for repeatable, structured processes where each step is known in advance.
### Who can create and manage routines?
Owners and Admins can create, edit, enable, disable, and delete routines. Contributors can view run history for routines in projects they're a member of.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sola.security/workspace/routines.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.