Skip to main content
Jobs are scheduled tasks that an agent or Maya runs on your behalf, either once or on a repeating interval. You can use them to generate daily reports, check data sources, send reminders, or trigger actions through connected apps. Jobs keep working even when you are not online, and they persist across every published version of an agent. You can view all of your jobs on the Jobs page. To configure jobs for a specific agent, open the agent, go to Configure, then select Jobs.

​
Job types and triggers

A job starts from either a schedule or an app event. Scheduled jobs let you set a start date, an optional end time, and excluded days. Integration event jobs begin when the connected app fires its trigger. You describe the task in plain language, just like a chat message, and the agent carries it out.

​
Statuses and filters

Each job appears with a status so you can see its health at a glance.

Active

The job is switched on and will run at its next scheduled time or when its trigger fires.

Paused

The job is switched off and will not run until you enable it again.

Needs attention

The job has failed five runs in a row, or its destination is no longer valid. Fix the cause, then resume it.

Completed

A one-time job that has already run appears here.
On the Jobs page, use the status filter to show only Active, Paused, Needs attention, Completed, or All jobs.

​
Run history and transcripts

Every job keeps a run history. Select a job to open its detail panel and see recent runs, their timestamps, and outcomes. For any run, you can open the transcript to read the exact messages the agent produced. This is useful for debugging, auditing results, or confirming that a task finished as expected.

​
Delivery destinations

When a job finishes, you can send its results to one or more destinations. If you do not choose a destination, the job still runs and its results are stored in the run history. Available destinations include:
  • A chat in the Kolmena web app, including swarm chats
  • A Telegram conversation
  • A Discord channel
  • A webhook URL
If a destination chat is deleted or a connected app is detached, the job will show Needs attention. Edit the job and choose a valid destination to resume it.

​
Limits and behavior

  • 25 open jobs per user (active or paused)
  • One run at a time per job. If a run is still going when the next one should start, the new run is skipped.
  • Shortest interval is 15 minutes.
  • Five consecutive failures automatically pause the job. Resume it after you fix the cause.
  • Jobs persist across all published versions of an agent. You do not need to recreate them when you publish a new version.

​
Common errors and what to do

​
Next steps

Create a job

Walk through creating a scheduled or event-triggered job step by step.

Configure your agent

Learn how publishing works and why jobs persist across versions.