> For the complete documentation index, see [llms.txt](https://docs.tagshelf.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tagshelf.dev/event-api/jobevents/job-failed.md).

# JobFailedEvent

## Usage

This event triggers when a job cannot proceed through its workflow, halting at a particular stage. Some reasons for this event triggering are the following:

* Incomplete document data preventing classification.
* Unrecoverable errors during extraction.

## JSON Payload

```json5
{
  "event_id": "(UUID format) - Unique identifier for the event.",
  "event_type": "Describes the type of event that occurred.",
  "event_time": "(floating-point numeric timestamp) - Unix timestamp representing the time when the event occurred, rounded to whole seconds.",
  "event": {
    "event_name": "Name of the specific event.",
    "event_type": "Type of the event, often matching or related to the outer event_type.",
    "company_id": "(UUID format) - Unique identifier for the company associated with the event.",
    "company_name": "Name of the company involved in the event.",
    "job_id": "(UUID format) - Unique identifier for the job that has failed.",
    "retries": "Integer - The number of attempts made to complete the job successfully.",
    "exceeded_retries": "Boolean - Indicates whether the number of attempts has surpassed the allowed threshold, which in this case is 'false', meaning more attempts might be possible.",
    "error_messages": "Array of Strings - List of error messages explaining the reasons for the job's failure, such as connectivity issues and timeouts, which help in troubleshooting.",
    "creation_date": "(ISO 8601 date format) - Date and time when the job was initially created.",
    "update_date": "(ISO 8601 date format) - Date and time when the job or event details were last updated."
  }
}

```

```json
{
  "event_id": "f3g4h5i6-j7k8-l9m0-n1o2-p3q4r5s6t7u8",
  "event_type": "job_event_type",
  "event_time": "1653139800.00",
  "event": {
    "event_name": "job_failed_event",
    "event_type": "job_event_type",
    "company_id": "34567890-4567-4567-4567-4567890123ef",
    "company_name": "Innovative Solutions",
    "job_id": "45678901-5678-5678-5678-5678901234fg",
    "retries": "3",
    "exceeded_retries": "false",
    "error_messages": [
      "Network connectivity issues",
      "Database timeout error"
    ],
    "creation_date": "2023-05-21T15:20:00Z",
    "update_date": "2023-05-21T16:40:00Z"
  }
}

```


---

# 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.tagshelf.dev/event-api/jobevents/job-failed.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.