> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/troubleshooting/i-get-a-0-tasks-labeled-alert-when-trying-to-pre-label-tasks.md).

# I get a "0 Tasks Labeled" alert when trying to pre-label tasks

Most likely, you are attempting to pre-label tasks which are not in the [*Start* stage](/core-concepts/workflow.md#start). Only tasks in the *Start* stage can be pre-labeled.

By default, tasks skip the *Start* stage and are automatically forwarded to the stage connected to the output of *Start*. This is visible in the *Workflow* tab, when a dotted line runs from the output of Start to the input of another stage:

<figure><img src="/files/LsJ91dcPGCJ4rFbdnTNr" alt=""><figcaption></figcaption></figure>

It is for this reason that by default, pre-labeling is disabled.

## How to Activate Pre-Labeling and Pre-Label Tasks

1. Go to the *Workflow* tab, then click on the *Start* stage and disable the *Auto Forward* toggle. This will ensure tasks remain in the *Start* stage when created. The dashed line will turn to a fully filled-in line.
2. [Import or upload your assets.](/data/importing-assets.md)
3. [Import your pre-labels](/data/importing-and-exporting-annotations/importing-annotations.md), ensuring the tasks you are trying to pre-label are currently in the *Start* stage.
4. When you are finished pre-labeling tasks, go to the Workflow tab again and click on the *Start* stage. Then, click on *Send All Tasks to Next Stage*. This will push all tasks in Start to the stage following it, sending them into the workflow.\
   ![](/files/HFCUrawYFUmvMWr3QV4l)


---

# 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.imerit.net/troubleshooting/i-get-a-0-tasks-labeled-alert-when-trying-to-pre-label-tasks.md?ask=<question>&goal=<endgoal>
```

`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.
