Executions
An execution is each time a task runs. It stores who triggered it, in which environment, with which parameters, everything the agent did and how much it cost.
Where a run comes from​
| Source | How |
|---|---|
| Console | Run now button (Run a task) |
| Schedule | the task's cron expression in an environment (Schedules) |
| API | POST /v1/tasks/{id}/run (API v1) |
| Endpoint | POST /run-task/{task_id} called by another system (Run endpoint) |
| Manage | run by the Kobana team |
The source appears in the Source column of Analytics → Logs.
Status​
| Status | In the console | Meaning |
|---|---|---|
queued | Queued | Accepted, waiting for the previous execution of the same task to finish. |
pending | Pending | Sent to run. The agent starts within 3 minutes. |
running | Running | The agent is working. |
success | Done | Finished and saved the result. |
failed | Failed | Finished with an error (the skill exited with a failure, timed out or could not start). |
cancelled | Cancelled | Interrupted by a person. What has already been done in external systems is not undone. |
One execution per task at a time​
Each task runs one execution at a time. A run while another execution of
the same task is in progress is not rejected: it joins the queue (queued)
and starts on its own when the previous ones finish. The console tells you how
many executions are ahead before you confirm.
Schedules are the exception: if the task already has an active or queued execution at the scheduled time, that run is skipped, not stacked. A cron shorter than the task's duration loses runs.
Different tasks run in parallel.
What an execution records​
| Tab | Content |
|---|---|
| Timeline | The timeline of events the skill emitted: start and end of each step, warnings and errors. |
| Logs | The log lines and the HTTP calls to external systems, with secrets masked. |
| Pending | What the skill left for a person to resolve. |
| Files | The input files attached to the run and the output files published by the execution. |
| Result | The final report in Markdown. |
| Cost | Tokens consumed (input, output, cache), tier and cost. |
See Follow an execution.
Limits​
- Time: an execution runs for up to 60 minutes. After that, it is interrupted and marked as failed.
- Plan and cost cap: without Kadu in the organization's plan, or with the monthly cost cap reached, the run is rejected. See Plan and costs.
- Retention: events, logs and webhook deliveries are kept for 90 days.