> 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.237/help-center-index/troubleshooting-index/errors-index/common-error-solutions/opshub-012075.md).

# OpsHub-012075

### Description

For OpsHub-012075, the following error message appears:

OpsHub-012075: Processing blocked - for the enitity `<entity-id>` because the other integration is trying to synchronize the data from this entity. You may need to retry this error once the processing of this entity is completed.

### Cause

* In the bidirectional integration between systems A and B, before <code class="expression">space.vars.OIM</code> processed the sync, the entity was updated in system B first when the entity was trying to sync to system A. In such a case, it leads to data inconsistency in the sync.
* To prevent this data inconsistency, <code class="expression">space.vars.OIM</code> blocks the processing of the entity.

### Solution

1. You may need to retry this failure once the processing of this entity is completed. For this, the sync logs can be analyzed to make sure that processing is completed for this entity.
2. Navigate to the integration for which this failure occurred. Retry the failure by clicking 'Retry All With Dependents' failure option. For more information on how to retry failure, refer to [Action on failures](/v7.237/help-center-index/troubleshooting-index/manage-integration-failures.md#action-on-failures) section.


---

# 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.opshub.com/v7.237/help-center-index/troubleshooting-index/errors-index/common-error-solutions/opshub-012075.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.