<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Error codes on Dapr Docs</title><link>https://v1-18.docs.dapr.io/developing-applications/error-codes/</link><description>Recent content in Error codes on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/developing-applications/error-codes/index.xml" rel="self" type="application/rss+xml"/><item><title>Errors overview</title><link>https://v1-18.docs.dapr.io/developing-applications/error-codes/errors-overview/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/error-codes/errors-overview/</guid><description>&lt;p>An error code is a numeric or alphanumeric code that indicates the nature of an error and, when possible, why it occured.&lt;/p>
&lt;p>Dapr error codes are standardized strings for over 80+ common errors across HTTP and gRPC requests when using the Dapr APIs. These codes are both:&lt;/p>
&lt;ul>
&lt;li>Returned in the JSON response body of the request.&lt;/li>
&lt;li>When enabled, logged in debug-level logs in the runtime.
&lt;ul>
&lt;li>If you&amp;rsquo;re running in Kubernetes, error codes are logged in the sidecar.&lt;/li>
&lt;li>If you&amp;rsquo;re running in self-hosted, you can enable and run debug logs.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h2 id="error-format">Error format&lt;/h2>
&lt;p>Dapr error codes consist of a prefix, a category, and shorthand of the error itself. For example:&lt;/p></description></item><item><title>Error codes reference guide</title><link>https://v1-18.docs.dapr.io/developing-applications/error-codes/error-codes-reference/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/error-codes/error-codes-reference/</guid><description>&lt;p>The following tables list the error codes returned by Dapr runtime.
The error codes are returned in the response body of an HTTP request or in the &lt;code>ErrorInfo&lt;/code> section of a gRPC status response, if one is present.
An effort is underway to enrich all gRPC error responses according to the &lt;a href="https://v1-18.docs.dapr.io/developing-applications/error-codes/grpc-error-codes/#richer-grpc-error-model">Richer Error Model&lt;/a>. Error codes without a corresponding gRPC code indicate those errors have not yet been updated to this model.&lt;/p></description></item><item><title>Handling HTTP error codes</title><link>https://v1-18.docs.dapr.io/developing-applications/error-codes/http-error-codes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/error-codes/http-error-codes/</guid><description>&lt;p>For HTTP calls made to Dapr runtime, when an error is encountered, an error JSON is returned in response body. The JSON contains an error code and an descriptive error message.&lt;/p>
&lt;pre tabindex="0">&lt;code>{
 &amp;#34;errorCode&amp;#34;: &amp;#34;ERR_STATE_GET&amp;#34;,
 &amp;#34;message&amp;#34;: &amp;#34;Requested state key does not exist in state store.&amp;#34;
}
&lt;/code>&lt;/pre>&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/error-codes/error-codes-reference/">Error code reference list&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://v1-18.docs.dapr.io/developing-applications/error-codes/grpc-error-codes/">Handling gRPC error codes&lt;/a>&lt;/li>
&lt;/ul></description></item><item><title>Handling gRPC error codes</title><link>https://v1-18.docs.dapr.io/developing-applications/error-codes/grpc-error-codes/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-applications/error-codes/grpc-error-codes/</guid><description>&lt;p>Initially, errors followed the &lt;a href="https://grpc.io/docs/guides/error/#standard-error-model">Standard gRPC error model&lt;/a>. However, to provide more detailed and informative error messages, an enhanced error model has been defined which aligns with the gRPC &lt;a href="https://grpc.io/docs/guides/error/#richer-error-model">Richer error model&lt;/a>.&lt;/p>


&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 Not all Dapr errors have been converted to the richer gRPC error model.

&lt;/div>

&lt;h2 id="standard-grpc-error-model">Standard gRPC Error Model&lt;/h2>
&lt;p>The &lt;a href="https://grpc.io/docs/guides/error/#standard-error-model">Standard gRPC error model&lt;/a> is an approach to error reporting in gRPC. Each error response includes an error code and an error message. The error codes are standardized and reflect common error conditions.&lt;/p></description></item></channel></rss>