> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.226/manage/mcp/mcp-sample-use-cases/mcp-use-case-retry-failures.md).

# View and Retry Failed Synchronizations

### Description

A user wants to review the processing failures across integrations and retry them without navigating to the <code class="expression">space.vars.OIM</code> UI. Processing failures are record-level failures — individual items that failed to sync — and can be re-queued for synchronization once the underlying issue is resolved.

### Example interaction

| Component               | Detail                                                                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **User prompt**         | "Show me the processing failures and retry them."                                                                              |
| **MCP tools invoked**   | `get_processing_failures_list` → `retry_processing_failures`                                                                   |
| **AI assistant steps**  | Retrieves failures with messages and item details → presents list for user review → retries on confirmation → reports results. |
| **AI assistant output** | A list of processing failures with failure details, followed by confirmation of which failures were successfully re-queued.    |

### Notes

* Global failures can be listed and retrieved for review.
* Updating `eventXML` for processing failures is not supported via MCP tools, as the `eventXML` contains actual source record data and modifying it could lead to unintended mutation of user data.


---

# 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:

```
GET https://docs.opshub.com/v7.226/manage/mcp/mcp-sample-use-cases/mcp-use-case-retry-failures.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.