> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.3/administration/job-workflow.md).

# Job Workflow

Job Workflows allow users to automate and organize repetitive data processing and retrieval tasks. These workflows streamline complex jobs by chaining a sequence of actions designed visually using drag-and-drop functionality.

**Key benefits of Job Workflows include:**

* **Organization:** Create structured workflows for intricate multi-step data jobs.
* **Automation:** Schedule recurring tasks to run automatically, saving time and effort.
* **Efficiency:** Streamline repetitive processes for improved data management.
* **Flexibility:** Design custom workflows tailored to your specific needs.

**Job Workflows offer a wide range of features:**

* **Diverse Job Types:** Integrate tasks like data acquisition (connectors, crawlers, SQL queries), data processing (profiling, quality checks), user management, custom scripts, and more.
* **User Permissions:**
  * OE\_Admin and Author users can create, edit, and execute workflows.
  * Viewers can design and save workflows for authorized users to execute.
* **Scheduling:** Schedule workflows to run automatically at specific times or intervals (OE\_Admin only).
* **Monitoring and Notifications:** Track workflow execution status and receive alerts upon completion (success, failure, or partial success).


---

# 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://docs.ovaledge.com/release8.3/administration/job-workflow.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.