> For the complete documentation index, see [llms.txt](https://data-programs.gitbook.io/singularity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://data-programs.gitbook.io/singularity/cli-reference/run/dataset-worker.md).

# Dataset Worker

{% code fullWidth="true" %}

```
NAME:
   singularity run dataset-worker - Start a dataset preparation worker to process dataset scanning and preparation tasks

USAGE:
   singularity run dataset-worker [command options]

OPTIONS:
   --no-automigrate      skip automatic database migration and correctness checks on startup; only use if you run 'admin init' on every upgrade or manually before starting daemons (default: false)
   --concurrency value   Number of concurrent workers to run (default: 1)
   --enable-scan         Enable scanning of datasets (default: true)
   --enable-pack         Enable packing of datasets that calculates CIDs and packs them into CAR files (default: true)
   --enable-dag          Enable dag generation of datasets that maintains the directory structure of datasets (default: true)
   --enable-reaper       Enable the orphan-record reaper. Exactly one dataset-worker process per deployment should enable this; running multiple reapers contends on the same rows and can livelock. (default: true)
   --exit-on-complete    Exit the worker when there is no more work to do (default: false)
   --exit-on-error       Exit the worker when there is any error (default: false)
   --min-interval value  How often to check for new jobs (minimum) (default: 5s)
   --max-interval value  How often to check for new jobs (maximum) (default: 2m40s)
   --help, -h            show help
```

{% endcode %}


---

# 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://data-programs.gitbook.io/singularity/cli-reference/run/dataset-worker.md?ask=<question>&goal=<user_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.