> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/dataos-resources/workflow/field-reference.md).

# Field reference

Use this page to look up Workflow manifest fields, required values, and nested options.

## Top-level fields

| Field         | Description                                      | Required |
| ------------- | ------------------------------------------------ | -------- |
| `version`     | API version of the Workflow resource.            | Yes      |
| `name`        | Unique name of the Workflow.                     | Yes      |
| `type`        | Resource type. Set this to `workflow`.           | Yes      |
| `tags`        | Labels used for grouping and filtering.          | No       |
| `description` | Short summary of the Workflow.                   | No       |
| `spec`        | Main configuration block for execution settings. | Yes      |

## `spec` fields

| Field                             | Description                                           | Required |
| --------------------------------- | ----------------------------------------------------- | -------- |
| `spec.type`                       | Execution mode for the Workflow. Commonly `instance`. | No       |
| `spec.use.projection`             | Workflow-level projections for secrets and config.    | No       |
| `spec.dependencies`               | Resource-level prerequisites before execution starts. | No       |
| `spec.schedule`                   | Scheduling configuration for automatic execution.     | No       |
| `spec.schedule.crons`             | One or more cron expressions for run timing.          | No       |
| `spec.schedule.timezone`          | Time zone used to evaluate the cron schedule.         | No       |
| `spec.schedule.concurrencyPolicy` | Controls whether overlapping runs are allowed.        | No       |
| `spec.dag`                        | List of batch steps in the Workflow DAG.              | Yes      |

## `spec.dag[]` fields

| Field                | Description                               | Required |
| -------------------- | ----------------------------------------- | -------- |
| `spec.dag[].name`    | Name of an individual step.               | Yes      |
| `spec.dag[].title`   | Optional human-readable title for a step. | No       |
| `spec.dag[].depends` | Step dependencies inside the DAG.         | No       |
| `spec.dag[].spec`    | Runtime configuration for that step.      | Yes      |

## `spec.dag[].spec` fields

| Field                                | Description                                      | Required |
| ------------------------------------ | ------------------------------------------------ | -------- |
| `spec.dag[].spec.compute`            | Compute target used for the step.                | Yes      |
| `spec.dag[].spec.resources.requests` | Minimum CPU and memory requested for execution.  | No       |
| `spec.dag[].spec.resources.limits`   | Maximum CPU and memory allowed for execution.    | No       |
| `spec.dag[].spec.runAsUser`          | User identity used to run the step.              | No       |
| `spec.dag[].spec.use.volumes`        | Mounted volumes available to the step.           | No       |
| `spec.dag[].spec.use.projection`     | Injected secrets and configuration for the step. | No       |
| `spec.dag[].spec.stack`              | Runtime stack used to execute the step.          | Yes      |
| `spec.dag[].spec.stackSpec`          | Stack-specific configuration details.            | Yes      |

## Notes

* Model the DAG first, then choose the runtime for each step.
* Use `spec.schedule` only when the Workflow should run automatically.
* Use Workflow-level `use.projection` for values shared across the run.
* Use step-level `use.projection` or `use.volumes` when only specific steps need them.

For behavior and usage guidance, see [Core concepts](/references/dataos-resources/workflow/core-concepts.md).


---

# 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://v2.dataos.info/references/dataos-resources/workflow/field-reference.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.