# Slow tasks

Sometimes pipelines become slow. And there are multiple reasons for this that in 95% of cases are external to Ylem:

* Slow processing of information on the database side
* Slow response from external networks
* Lack of resources to process pipelines that conflict with each other

The last point is especially important if you have too many slow pipelines they start conflicting and waiting for available cluster resources to process them. It causes delays and slows down the performance.

Therefore we introduced a [slow task profiling tool](https://app.datamin.io/slow-tasks).

<figure><img src="/files/jBp7hBkAgtPey8Iv6bG8" alt=""><figcaption><p>Example of how to profile slow Aggregators within a certain data range</p></figcaption></figure>

With this tool, you will always be aware of slow tasks and queries, failed workflow runs, and incorrect inputs/outputs.

You can play with a [type of the task](/pipelines/tasks-ip.md), a data range, and a processing threshold in milliseconds. As a result, it will show you what tasks of what pipelines took more time to process than milliseconds when it was executed, and what output it returned. Having this information you can look deeper into your infrastructure and improve the performance of your pipelines.


---

# Agent Instructions: 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:

```
GET https://docs.ylem.co/statistics-and-profiling/slow-tasks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.