> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/monitoring/task-usage.md).
# Task Usage
## Task Usage
The Task Usage page shows Workflow, Playbook, and testing task consumption across your workspace. To view this screen, open **Monitoring** from the left sidebar and select **Task Usage**.
## Monitoring Task Usage
* Each Workflow or Playbook is displayed with metrics including average tasks per run, total tasks used, and percentage of your overall workspace consumption.
* Testing task usage shows how much of your free testing task balance has been used while iterating in the Workflow Studio or Playbook editor.
* Tracking high-consumption runs helps you optimize task allocation and manage costs.
* Use the date range selector in the top right to analyze usage patterns over specific time periods.
* The bar chart visualization shows task distribution across your Workflows and Playbooks.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.airops.com/your-workspace/monitoring/task-usage.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.