Jobs let you define arbitrary agent work that can be run on demand or scheduled. Use Jobs when the instruction is useful enough to repeat, monitor, or hand to an agent without rewriting it every time.
Open Jobs from Agent → Jobs.
When to use Jobs
Use a job for work such as:
- Reviewing a dashboard and updating commentary
- Creating a weekly performance summary
- Checking a dataset, report, or pipeline for issues
- Running an analysis with the same instruction each month
- Preparing a draft note for a team or stakeholder group
- Asking an agent to inspect a platform asset and recommend next steps
Use a conversation instead when you are still exploring the question interactively.
Job definitions and runs
The Jobs page has two main views:
- Job definitions: reusable instructions, assignee, context, schedule, and notification settings
- Runs: execution history for jobs, including step details and results
A job definition can be run manually with Run now. If a schedule is enabled, TrueState creates runs from the cron schedule.
Create a job definition
To create a job:
- Open Agent → Jobs.
- Click Create job definition.
- Choose the agent assignee.
- Give the job a clear name.
- Write the instruction.
- Add relevant context assets.
- Optionally enable a schedule and notifications.
Example instruction:
Review the Revenue Overview dashboard every Monday morning. Compare performance with the previous full week, identify the three most important changes, and update the dashboard commentary with concise bullets for the leadership team.
Add context to a job
Attach the assets the agent should use. Useful context might include:
- A dashboard to inspect
- A dataset to query
- A report to update
- A pipeline to check
- A document with stakeholder requirements
- A model or deployment relevant to the work
Also keep durable assumptions in Agent → Context so future jobs and conversations start from the right business knowledge.
Scheduling
Jobs can run without a schedule or with scheduling enabled. The schedule uses cron syntax.
Common examples:
| Schedule | Meaning |
|---|---|
0 9 * * 1 | Every Monday at 9:00 |
0 8 1 * * | 8:00 on the first day of each month |
0 17 * * 5 | Every Friday at 17:00 |
If schedule timing matters, confirm the organisation's expected timezone with your administrator.
Inspect runs
Open the Runs tab to inspect job execution history. A run can include multiple steps, intermediate outputs, final results, and error states.
This is useful for debugging a job instruction. If a run does the wrong thing, update the job definition with clearer context, stricter output requirements, or a narrower task.
Best practices
- Write the instruction as if briefing a capable analyst.
- Name the output location when the job should update something.
- Attach the exact dashboard, report, dataset, or pipeline the job should use.
- Keep recurring jobs narrow and auditable.
- Use notifications for jobs where a human should review the output.
- Review early runs before trusting a schedule.