One of the following:

• An invalid 64-bit code was found while parsing a U64JSON value.
• The explicit size of an array, which was used to skip the array, is inconsistent with the array contents.
• The explicit size of an object, which was used to skip the object, is incorrect.
• Duplicate keys appear in an object.
• The container length exceeds the length of the available data or the container length is shorter than the available data.
• A number as a string has a parse error.

A malformatted request was received. For example, the params member is an array instead of an object.

This error is only returned when the request is sufficiently well-formatted to identify that it is a request, for example it contains a method member, and to enable the return path to be traced back. Requests that contain an invalid or missing method, instId, or request id might not be able to respond to the caller.

A function was called with a valid instId argument, but the instance does not support the function that was called.

This error applies only to the function name, not to arguments or their values. This error is also returned when an unsupported global function, without an instId, was called.

A function received one or more argument names that it does not support. This error tells the caller that the expected functionality is not available in the function. The caller can fall back to a simpler function call with fewer parameters, if it is designed to do so.

The callee must put an object {"name": X} into error.data of the response object, where X is one of the unsupported argument names. This does not imply that other argument names are valid.

A function received an unsupported value for one or more arguments. This is a catch-all error code, which should only be used if a more specific error code is not available.

The callee must put an object {"name": X} into error.data of the response object, where X is the name of one of the arguments containing an unsupported value. This does not imply that other argument values are valid.

A function was called without a mandatory argument.

The callee must put an object {"name": X} into error.data of the response object, where X is one of the missing argument names. This does not imply that all other arguments are present.

A value of an incompatible type was specified for a function parameter. This includes types of object members that are passed into functions.

See 3.1 JSON data types for type compatibility and conversion rules.

The callee must put an object {"name": X} into error.data of the response object containing the parameter name of one of the errors encountered. This does not imply that other parameters are valid.

It is undefined whether the request was ignored or partially completed. Clients should assume that the request was ignored and should repeat the request.

The function being called or the feature being requested or used is not implemented.

A common use case is to return this in the error member of a ResourceReadResult or ResourceWriteResult for resources that are known to an instance but are not implemented. It might be more useful to return E_not_implemented rather than returning dummy values for partially implemented interfaces during development.

Iris functions should generally not return this error for functionality that will never be implemented. E_function_not_supported_by_instance or the E_*unsupported* errors should be preferred if they are more appropriate.