Skip to content

/problems/resource-modified⚓︎

Problem

This is a description of a specific error response that you can receive when using the INVERS OneAPI via REST.1

Check out our API Basics to learn more about the basic structure of all error responses and to find out how you should handle them.

{
    "type": "/problems/resource-modified",
    "type_documentation": "https://developers.invers.com/problems/resource-modified",
    "title": "Resource has been modified.",
    "status": 412,
    "detail": "…",
    "flow_id": "5e77e3e3-48ab-4955-8ab3-1c62339096ab"
}

Meaning⚓︎

This problem type occurs if the resource you want to change has already been modified.

Details⚓︎

  • Use the error response’s type property to handle specific errors and exception handling within your application. It’s comparable to an error code.
  • The detail property contains additional, more human-readable information about the problem or error. This is explanatory text and you should not have any exception handling and error handling code depend on it, as it may change.

Detail examples⚓︎

The following examples are typical texts which you might receive in the error response’s detail property. Note that it is not a complete list of all possible cases. Therefore expect to receive error responses with a detail property value not listed below.

If-Match header does not match. This means that this resource has been modified since the requested Etag sent as If-Match header was issued. Please get or reload the current resource and Etag to try again.

Your have specified an If-Match header in your request, but it does not match.

Possible solutions:

  • Check if you have transmitted the ETag correctly, as shown in this example
  • Check if there are any additional or unwanted characters besides the ETag in your If-Match header
  • Check if you have transmitted the complete ETag

Further reading⚓︎

  1. The flow_id is specific to each API call, so it will be different in your case. However, type, title and status will match your actual error response if you receive the error described on this page. ↩