> For the complete documentation index, see [llms.txt](https://docs.taskforce.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskforce.sh/connections/jobs.md).

# Jobs

The jobs view allows you to examine jobs that are in the queue or that have been processed by the workers. You can select any of the possible states where a job can be in a queue to discover which jobs are in said states:

![](/files/-MWPC2mK6Fzu-bOPOtK1)

Jobs can be opened in order to get useful information such as: options, data, result values, logs, error callstacks and reasons for failing:

![](/files/-MWPCYYu1abAioQeAvrH)

From this view it is also possible to perform operations on the individual jobs, or on a certain selection of the jobs.

![Job action menu](/files/-MWPDQTg-8zUug-mHJre)

For example, a common action is to retry failed jobs after resolving the underlaying reason for the failure.

#### Updating jobs

It is possible to edit the data of existing jobs if they are in *compatible* states such as "Waiting", "Delayed" or "Failed". You update a job by clicking on the "Edit" icon:

![](/files/-MePCBLYLKkaVBlJGyw7)

You will get up an update job dialog:

![](/files/-MeOue3sr7sE8FZD4U2v)

Just perform any change you want on the data field as JSON and click on Update:

![](/files/-MeOvLaQPhtaGSK6Rcrn)


---

# 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://docs.taskforce.sh/connections/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.