> ## Documentation Index
> Fetch the complete documentation index at: https://agents.nanonets.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Running tasks

> Start an agent run, follow its progress, answer questions, and review the result.

A task is one run of an agent.

For example, if an invoice agent reviews five invoices, that is five tasks.

<Frame caption="A task feed: your request at the top, each step the agent ran (Extract invoice fields, Check the vendor), and the final result.">
  <img src="https://mintcdn.com/nanonets-fb7e8f2a/eksLpltcNl29FEi2/images/task-feed.png?fit=max&auto=format&n=eksLpltcNl29FEi2&q=85&s=49861ad6a8786c665b6824d096228a06" alt="Task feed showing the agent's steps and final result for an invoice" width="1440" height="1100" data-path="images/task-feed.png" />
</Frame>

## Start a task

You can start a task in a few ways:

* Start it manually from the agent.
* Upload a file and ask the agent to process it.
* Let a trigger start it, such as a new email or a schedule.
* Start it from an app or API if your team has set that up.

## Follow the task feed

The task feed shows the agent's work step by step.

You may see:

* Files the agent read.
* Data the agent extracted.
* Lookups it performed.
* Questions it asked.
* Files or messages it created.
* Final results.

## When the agent asks a question

Sometimes the agent needs help.

It may ask because a field is missing, a result is unclear, or your rules require human input.

<Frame caption="When the agent needs input, the task pauses with a 'Waiting for user input' prompt. Reply in the box to continue.">
  <img src="https://mintcdn.com/nanonets-fb7e8f2a/eksLpltcNl29FEi2/images/paused-task.png?fit=max&auto=format&n=eksLpltcNl29FEi2&q=85&s=e7f1c7ea3958017b5d3c540992bd85f4" alt="A paused task showing the agent's question and a Waiting for user input prompt" width="890" height="240" data-path="images/paused-task.png" />
</Frame>

When this happens:

1. Read the question.
2. Check the document or context if needed.
3. Reply with the missing information.
4. The agent continues the task.

## When a task needs review

Some tasks pause for approval.

This is useful for payments, customer messages, system updates, or anything your team wants a person to check first.

<Frame caption="A task awaiting review: the agent explains the decision and pauses with Approve, Request changes, and Reject actions.">
  <img src="https://mintcdn.com/nanonets-fb7e8f2a/eksLpltcNl29FEi2/images/awaiting-review.png?fit=max&auto=format&n=eksLpltcNl29FEi2&q=85&s=1f8cabb5e23c9590f3d4dbaaa7c655db" alt="A task awaiting review showing a payment approval prompt with Approve, Request changes, and Reject actions" width="690" height="340" data-path="images/awaiting-review.png" />
</Frame>

Review the result, then approve or reject it based on your team's process.

## Common task states

| State             | What it means               | What you should do               |
| ----------------- | --------------------------- | -------------------------------- |
| Running           | The agent is still working. | Wait or watch the feed.          |
| Waiting for input | The agent asked a question. | Reply in the task.               |
| Awaiting review   | A human approval is needed. | Review and approve or reject.    |
| Completed         | The task is done.           | Check the final result.          |
| Failed            | Something went wrong.       | Review the feed or ask an admin. |

## Improve the next run

After a task finishes, look for repeated corrections.

If you keep fixing the same thing, add a rule so the agent can handle it next time.

Learn more in [Rules](/docs/guide/rules).