Developer

Error Handling

When a request fails against the backend OData Service during a flush operation, the request and any relevant details are stored in the ErrorArchive.

Error State

Any entities or links in the Offline Store that were affected by the failed request are moved into an Error State. The error state indicates that the state of the entity or link in question may not be valid and needs to be fixed before proceeding.

Entities and links that are in an error state are distinguished by the presence of the inErrorState annotation. If the failing request had the effect of deleting an entity or link, they will reappear in the Offline Store and contain the additional isDeleteError annotation.