> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.propexo.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.propexo.com/_mcp/server.

# Job Failure Webhook

The **JOB\_FAILURE** webhook is sent when an integration fails to retrieve data after multiple retry attempts. This event alerts you that a scheduled or triggered job was unable to complete successfully, which may require investigation or remediation.

## When It Triggers

A JOB\_FAILURE webhook is triggered in situations such as:

* An API outage or downtime in the connected property management system.
* Authentication or authorization failures preventing data retrieval.
* Data fetch requests timing out repeatedly.

This event typically occurs after Propexo has made several retry attempts without success.

## Common Use Cases

* **Alerting internal teams** so they can quickly investigate and resolve the issue.
* **Logging failures** for audit purposes, SLA tracking, or error reporting dashboards.

## Example Payload

```json
{
  "event": "JOB_FAILURE",
  "integration_id": "INTEGRATION_ID_002",
  "job_id": "JOB_ID_002",
  "job_type": "READ_RESIDENT_TRANSACTIONS",
  "root_job_id": "ROOT_JOB_ID_002",
  "vendor": "RESMAN"
}
```

## Field Reference

* **event** – The webhook event type.
* **integration\_id** – Unique ID for the integration.
* **job\_id** – The ID of the failed job.
* **job\_type** – The type of job attempted.
* **root\_job\_id** – The root job that initiated the process.
* **vendor** – The PMS vendor for the integration.