> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/features/runs/scheduling.md).
# Scheduling runs
How to schedule runs in ion and view your factory schedule
### Scheduling and assigning a run
Runs have multiple steps. Each step is can be unique and will have their own lead time and schedule. In the summary view for a run (Runs -> Click on a run), you can schedule each step's start and end schedule, along with a lead time.
Scheduling both an individual step, along with the entire run
{% hint style="info" %}
If the run start time and end time are not set but individual steps in the run have start and end times set, the run will automatically set its start and end times to the earliest start and the latest end.
{% endhint %}
### Viewing production schedule
From the main **Runs** view, click on the Timeline button on the top. Here, you can see all of the runs scheduled in your factory in a Timeline. Below the chart, you can see unscheduled runs.
Clicking one of the items in the left column will pop out the right side and allow you to schedule the run. The timeline window will reflect your changes automatically.
---
# 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://manual.firstresonance.io/features/runs/scheduling.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.
