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

# Write Operation Failure Webhook

The **WRITE\_OPERATION\_FAILURE** webhook is sent when an integration fails to write data to the connected property management system. This event alerts you that a write operation was unable to complete successfully, which may require investigation or remediation.

## When It Triggers

A WRITE\_OPERATION\_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 writes.
* Data write requests timing out.
* Validation errors or data conflicts in the target system.

## 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
{
  "trigger": "WRITE_OPERATION_FAILURE",
  "data": {
    "event": "WRITE_OPERATION_FAILURE",
    "integration_id": "INTEGRATION_ID_002",
    "vendor": "RESMAN",
    "root_job_id": "ROOT_OPERATION_ID_002",
    "write_status": "PARTIAL_SUCCESS",
    "errors": [
      "Failed to write resident transaction: Duplicate transaction ID"
    ]
  }
}
```

## Field Reference

* **trigger** – The webhook trigger type.
* **data** – The payload data object containing event details.
  * **event** – The webhook event type.
  * **integration\_id** – Unique ID for the integration.
  * **vendor** – The PMS vendor for the integration.
  * **root\_job\_id** – The root job that initiated the process.
  * **write\_status** – The status of the write operation (e.g., `PARTIAL_SUCCESS`, `FAILURE`).
  * **errors** – Array of error messages describing what went wrong.