> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/mailscheduler/features/monitoring.md).
# Monitoring
The Monitoring tab shows the results of tasks, the active tasks currently being executed, and any failed tasks. Failed tasks can be re-triggered in case of temporary issues or examined further. The results tab is improved. Now, all sub-tasks are shown here. If anything goes wrong, we track users who have already received an email. Hence, once we resend it, it will only be sent to users who have not received an email before.
#### Cancel running tasks
It's possible that you no longer want a task to execute while it's running. To do this, click on the X next to a running task, and confirm that you want to cancel the task. This will take a while to process, and then cancel the task run.
The task will then be stopped with the following status:
This feature is only available for Administrator users. Normal users will not see the button to cancel the execution of a task.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/mailscheduler/features/monitoring.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
