Developer

Fixing Requests in an Error State

When an entity or link is in the error state, the application has an opportunity to fix the error before reattempting the request.

To do this, the application can make additional modification requests to correct the data.

When fixing failed requests, the application does not need to consider the sequence of OData operations that put the store in the error state, but only needs to apply new operations to adjust the data to be correct in the local store. When the application executes a flush, the Offline Store analyzes the state of the error entities and links in the local store and computes the necessary operations to apply to the backend to achieve that state.

It is important to note that the offline store computes these operations based on its own heuristics and may not apply any of the original requests. Conceptually, the application is fixing the data and not the failed requests. This must be considered if there is backend business logic or side-effects that rely on specific OData operations being applied.

If the application does nothing to fix the error then the following flush resends the requests without making any changes.