# Workflows

A workflow is a configurable automated process made up of one or more job, task, or action call. You must create a YAML file to define your workflow configuration.

## Workflow *kinds*

There are two *kinds* of workflows: *live* and *batch*.

### *Live* workflows

[*Live*](https://docs.apolo.us/index/apolo-flow-reference/workflow-syntax/live-workflow-syntax#live-workflow) workflows are executed locally on the developer's machine. They contain a set of job definitions that spawn jobs in the Apolo cloud.

Here's an example of a typical job:

1. Executing a Jupyter Notebook server in the cloud on a powerful node with a lot of memory and a high-performant GPU.
2. Opening a browser with a Jupyter web client connected to this server.

### *Batch* workflows

[*Batch*](https://docs.apolo.us/index/apolo-flow-reference/workflow-syntax/batch-workflow-syntax) workflows serve for orchestration of a set of remote tasks that depend on each other. *Batch* workflows are executed by the main job that manages workflow graphs by spawning required jobs, waiting for their results, and starting dependent tasks when all of their requirements are satisfied. When possible, operations inside the batch runner will be re-ran on failing to ensure maximum batch stability.


---

# 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.apolo.us/index/apolo-flow-reference/readme.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.