> For the complete documentation index, see [llms.txt](https://oiadocs.cloudfabrix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oiadocs.cloudfabrix.io/features-guide/rda/explore/jobs.md).

# Jobs

In cfxOIA RDA context, the pipeline mechanism is supported via RDA bots which were explained in the previous section. RDA bots are designed, implemented, and logically connected to solve real-world problems.  

cfxOIA RDA pipelines are executed via manually triggering the pipeline or via schedules. Users can use one of the mechanisms to trigger a pipeline. Once the pipeline is triggered, RDA treats the execution unit as a 'Job'. Job is a logical representation of pipeline execution during runtime (within cfxOIA RDA environment).

Each job can be a simple 'Hello World' pipeline to medium to complex pipelines (e.g. Nagios pipeline, vrOPS pipeline, etc to name a few). Users will be able to execute these and other pipelines using 'Jobs'.

RDA provides the following jobs UI to allow users to view jobs status and details.

![Screenshot depicts jobs UI](/files/-MaRR7Cs0s0Ic2xOYUDw)

Users can use the following screenshot as a reference for various job's statuses

![Job status UI ](/files/-MaRS1KiZyQ1klhGyfDF)


---

# 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://oiadocs.cloudfabrix.io/features-guide/rda/explore/jobs.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.