> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.4/kaiya/kaiya-missions/missions-built-before-tellius-6-4.md).
# Missions built before Tellius 6.4
Run, schedule and change a Mission built before Tellius 6.4 in the Unified Chat, and bring it up to date with a Rich Summary step and a clear export step.
Missions built in a Kaiya conversation before Tellius 6.4 keep working in Tellius 6.4. You don't need to rebuild or reconfigure them. Their steps, run history and schedules carry over, and they run on the new engine as they are. When you want to change one, you open it in the Unified Chat, the same Kaiya conversation you use for everything else, with the Mission in a panel beside it.
{% hint style="info" %}
This page covers Missions built in a Kaiya conversation. Missions built in the form-based Classic Editor also keep running on their schedule, and open as read-only reference. See [Kaiya Missions](https://help.tellius.com/kaiya/kaiya-missions).
{% endhint %}
### **What carries over**
* **Steps.** The Mission runs the steps it was saved with. Input steps still ask for their values when the Mission runs from **Run** or from the conversation, and the summary step still follows the instructions saved in it. If a step still holds placeholder values from earlier releases, Kaiya fills them in on its own during the run, and may suggest updating the plan so later runs don't need this.
* **Run history.** Every earlier run stays in **RUN HISTORY** on the Mission's page, and each one keeps the briefing it produced at the time. A briefing from before Tellius 6.4 keeps its earlier look, such as chart cards and a bullet list of findings.
* **Schedules.** Existing schedules keep running at the same times and send to the same places. Scheduled runs show as **Scheduled** in the run history, next to **Run manually** runs.
* **Export steps.** A Mission that ends with an export, such as a PowerPoint deck or a PDF report, still produces it, following the instructions in its export step.
### **Run the Mission and read the briefing**
Open **Missions** in the left navigation and select the Mission's card. Its page opens on the latest briefing. Select **Run** to start a run. The run opens in a Kaiya conversation and starts straight away.
Open the run selector at the top right to see **RUN HISTORY**: the number of runs, the share that succeeded and the average run time, then one row for each run. Select a row to show that run's briefing.
A briefing from a run in Tellius 6.4 has these parts:
* **How Kaiya got this:** the work behind the run. The header shows **Done** and how long the run took. Expand it to see what Kaiya did. Some runs also show an investigation bar with **Show plan**.
* **Mission steps:** each step that ran, with its number, its type and what it does, and a check mark once it completed. The header shows how many steps completed, for example **3 of 3 steps**. Expand a step to see more.
* **The summary:** a short written result with citation numbers beside the figures, and **Based on** with the Business View the run used.
* **The visual summary page,** when the Mission has a **Rich Summary** step: a headline, the period and source, cards for the key figures and charts.
* **Continue this conversation in Kaiya:** opens the run in a Kaiya conversation, so you can ask follow-up questions about it.
For every control on the page, see [Opening a Mission from the Mission Library or the home page](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission/mission-library-and-mission-page#opening-a-mission-from-the-mission-library-or-the-home-page).
### **Change the Mission in the conversation**
1. On the Mission's page, select **Configure**.
2. The Mission's conversation usually opens in the Unified Chat, with its earlier history. Kaiya scrolls to the message that built the Mission and opens the Mission panel on the right.
3. Ask for the change in plain language, for example *"Use the existing customer segments, and treat the highest tier as top-tier."*
{% hint style="info" %}
If the Mission panel doesn't open, select **OPEN MISSION** on the Mission card in the conversation, or go back to the Mission's page and select **Configure** again.
{% endhint %}
The panel header has a **Version** picker. Each version shows its number, a **Published** badge, when it was published, and **Active** on the version that runs. A Mission built before Tellius 6.4 starts at **V1**.
* On the **active** version, the **Analysis Steps** card on the **Steps** tab shows **Locked**. It can't be changed or reverted.
* On an **earlier** published version, the card shows **Read-only**. Use it to see how the Mission used to work.
* Your changes go into a **draft**, the next version number. If a draft already exists, Kaiya points you to it. You can also edit a step in place in the panel. The edit shows in the conversation as an **\[Inline edit]** note, and Kaiya checks whether any later step needs to change too.
Kaiya runs the draft in the conversation so you can check the result. That run is only a preview. Until you publish, every run from **Run**, every trigger and every schedule still uses the active version.
To publish, ask Kaiya, for example *"Publish this version so every run and schedule uses these steps."* The draft becomes the active version. The Mission's existing schedule uses the new steps on its next run, so you don't need to create the schedule again. Kaiya confirms the schedule in its reply and offers next steps under **ACTIONS**, such as running the Mission now.
If the Mission changes while you have it open, a banner at the top of the panel says the mission has changed since you opened it. Select **View latest** to load the newest version.
{% hint style="success" %}
**Edit in a draft, or start a new Mission?** Edit the Mission in a draft when you are improving the same job: the change goes live in one step, and the run history, triggers and schedules stay with the Mission. Start a new Mission, or select **Duplicate** in the Mission's three-dot menu, when the new version answers a different question or serves a different audience and both should keep running.
{% endhint %}
### **Recommended: replace the Summary step with a Rich Summary step**
Missions built before Tellius 6.4 usually end with a **Summary** step. It writes the briefing from the instructions saved in the step: the narrative, tables and charts, one after another. New Missions end with a **Rich Summary** step instead. It builds a visual summary page, and the run's reply in the conversation gives a short summary with a **Visual summary** card that opens the full page. On the Mission's page, the briefing shows the visual summary.
To move an older Mission to a Rich Summary step:
1. Select **Configure** on the Mission's page.
2. Ask Kaiya, for example *"Replace the summary step with a rich summary."* Describe what the visual summary should show, if you like, such as the key figures and the charts you want.
3. Kaiya saves the change as a draft and shows the new **Visual summary** card. Open it to check the page.
4. Ask Kaiya to publish the version. The next run, manual or scheduled, produces the visual summary.
{% hint style="info" %}
**Why move to Rich Summary?** A long text summary with charts in between is hard to scan: readers scroll up and down to compare figures. A visual summary puts the headline, the key figures and the charts on one page, so the result is quicker to read. The Mission's other steps don't change, and its schedule keeps running.
{% endhint %}
### **Recommended: put the export details in the export step**
When a Mission produces a file, such as a PowerPoint deck or a PDF report, write what the file should hold in the Mission's export step:
* **Storyline:** the order of the story, from the headline to the recommendations.
* **Contents:** the sections or slides, the figures and charts each one shows, and how many slides or pages there should be.
* **Design:** the layout, colours and fonts, and any logos, with a link to each logo and where it goes.
Every run then produces the same kind of file. To change the file later, change the export step's instructions, for example by asking Kaiya in the Mission's conversation.
The export step comes first. A custom skill, such as your organization's house format for decks, still applies to everything the export step leaves open. Where the two disagree, the export step's instructions win. See [Kaiya Skills](https://help.tellius.com/kaiya/kaiya-skills).
{% hint style="success" %}
**Not sure where a detail came from?** Ask Kaiya about the file, for example *"Where did the logo on the cover come from?"* Kaiya tells you whether it came from the export step or from a skill, so you know what to change.
{% endhint %}
### **Schedules**
Creating a schedule starts the same way as before. On the Mission's page, open the three-dot menu and select **Create Schedule**. **Scheduled Missions** opens, filtered to this Mission, with any schedules it already has. Select **Schedule** to add one. The form opens with the Mission filled in. If the Mission has input steps, selecting **Create Schedule** opens the schedule's conversation, where Kaiya runs the Mission up to each input step and asks you for the value, or for a hint on how to choose it. Kaiya reuses your answers on every scheduled run. Every run of the schedule then appears in that one conversation. See [Scheduling Missions](https://help.tellius.com/kaiya/kaiya-missions/scheduling-missions).
You can also ask Kaiya in the Mission's conversation, for example *"Run this every day at 6 AM."* When the Mission already has a schedule, Kaiya changes that schedule rather than adding a second one. Ask Kaiya to show the schedule's details, such as its cadence, start date, delivery and recipients.
{% hint style="warning" %}
A scheduled run can't search the web, and Python steps can't call outside services. A Mission reads data from Business Views, Kaiya Context Models, connected systems and indexed documents. Plan the data a Mission needs with that in mind.
{% endhint %}
### **Best practices**
* **Run it once after the upgrade.** Select **Run** and read the new briefing. Nothing needs to change for the Mission to work.
* **Move to Rich Summary when readers scan the briefing.** It is the quickest improvement for a Mission that ends with a long text summary.
* **Keep the export instructions in the export step.** One place to change the file makes every run consistent.
* **Publish on purpose.** Runs and schedules use the active version, so publish once the draft's preview looks right.
### **Related pages**
* [How to create a Kaiya Mission](https://help.tellius.com/kaiya/kaiya-missions/how-to-create-a-kaiya-mission)
* [Scheduling Missions](https://help.tellius.com/kaiya/kaiya-missions/scheduling-missions)
* [Best practices](https://help.tellius.com/kaiya/kaiya-missions/best-practices)
* [Apps built before Tellius 6.4](https://help.tellius.com/kaiya/kaiya-apps/apps-built-before-tellius-6-4)
---
# 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://help.tellius.com/tellius-6.4/kaiya/kaiya-missions/missions-built-before-tellius-6-4.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.
