> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workloads

> Turn a query into a repeatable workflow. Define tasks, connect their dependencies, choose compute, and decide when each run should happen.

ExplanationApplies to: Unified engine deployments

Turn a query into a repeatable workflow. Define tasks, connect their dependencies, choose compute, and decide when each run should happen.

A workload can run manually, once at a chosen time, on an interval, or on a cron schedule. Add sensors for external conditions, retry policies for eligible failures, and notifications for important events. Use data windows and backfills to process time periods explicitly.

## Start with a working example

1. [Your first workload](https://docs.e6data.com/transformation/workloads/first-workload.md): run one SQL task with six inline orders.
2. [Build a multi-task workflow](https://docs.e6data.com/transformation/workloads/multi-task-workflow.md): pass rows, run parallel tasks, and combine results.
3. [Parameters and query context](https://docs.e6data.com/transformation/workloads/parameters.md): reuse the same definition with different inputs.
4. [Schedules and time zones](https://docs.e6data.com/transformation/workloads/schedules.md): turn a manual workflow into recurring work.
5. [Publish a table result](https://docs.e6data.com/transformation/workloads/publish-results.md): write to Iceberg and verify the committed output.

The first examples use `WITH … VALUES`. They need a running engine, workload access, and available compute. They do not need files, a catalog connection, credentials, or external data. Publication and external integrations list their own setup requirements.

## Understand the moving parts

| Term | Meaning |
| - | - |
| Workload | The saved tasks, dependencies, parameters, schedule, and execution options. |
| Revision | A saved version of the definition. Editing creates a new revision. |
| Occurrence | One request to run the workload, such as a scheduled due time or manual submission. |
| Run | One execution of a recorded definition and invocation. |
| Task | One SQL query, Python program, or sensor within the workflow. |
| Attempt | One execution attempt for a task. A retry adds an attempt within the same run. |
| Data window | The period of data a run is meant to process. It can differ from the time the run starts. |

The scheduler creates run requests. The controller manages run progress and task dependencies. Workers execute task attempts. A scheduled due time is not a promise that a worker starts at that exact moment.

## Choose your next step

| You want to… | Read |
| - | - |
| Control order or share rows | [Tasks and dependencies](https://docs.e6data.com/transformation/workloads/tasks-and-dependencies.md) |
| Choose workers and limits | [Compute and execution limits](https://docs.e6data.com/transformation/workloads/compute.md) |
| Handle slow or missed runs | [Overlap, missed runs, and queues](https://docs.e6data.com/transformation/workloads/concurrency.md) |
| Process time periods | [Data windows](https://docs.e6data.com/transformation/workloads/data-windows.md) and [Backfills](https://docs.e6data.com/transformation/workloads/backfills.md) |
| Wait for another system | [Sensors](https://docs.e6data.com/transformation/workloads/sensors.md) |
| Recover part of a workflow | [Retry policies](https://docs.e6data.com/transformation/workloads/retries.md) and [Selective reruns](https://docs.e6data.com/transformation/workloads/reruns.md) |
| Receive callbacks | [Notifications](https://docs.e6data.com/transformation/workloads/notifications.md) |
| Explain a run's behavior | [Inspect runs and attempts](https://docs.e6data.com/transformation/workloads/runs.md) and [Troubleshooting](https://docs.e6data.com/transformation/workloads/troubleshooting.md) |
| Find exact request fields | [Definition and API reference](https://docs.e6data.com/transformation/workloads/reference.md) |

## Run examples in the product

Use the complete definitions below each example to create workloads in the Workload Editor or through HTTP. Review the tasks and dependencies, validate the definition, save it, then start a run. Keep practice schedules Manual until you choose to enable recurring execution. Saved workloads and started runs remain in the engine after you leave the console.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.