# Error Codes

Rierino elements trigger different error codes with related information provided in their result payload (such as record id responsible for error). Some of these errors also include root cause information (e.g. triggering system exception message). It is possible to create conditional flows or change error details within a Saga, this page lists information on raw error codes raised by different runner elements.

## Handler Errors

All handler error codes start with "10", and are triggered by handler runner elements.

<table><thead><tr><th width="100">Code</th><th width="269">Name</th><th>Description</th></tr></thead><tbody><tr><td>10001</td><td>Action/role not supported</td><td>Handler does not support the requested action or role</td></tr><tr><td>10002</td><td>Event version not supported</td><td>Handler does not support the requested event version</td></tr><tr><td>10004</td><td>Failed to generate id</td><td>Id generator failed to produce a new id</td></tr><tr><td>10005</td><td>Can not clear cache</td><td>Cacheable handler failed to clear its cache (e.g. on command)</td></tr><tr><td>10006</td><td>Input element not defined</td><td>Request event is missing input payload on given input element path</td></tr><tr><td>10008</td><td>Missing input payload</td><td>Request event is missing input payload on given input element path</td></tr><tr><td>10009</td><td>Missing parameter</td><td>Request event is missing a mandatory metadata parameter</td></tr><tr><td>10010</td><td>If pattern failed for edit</td><td>Edit action has a validity condition which current request fails to meet </td></tr><tr><td>10011</td><td>Can not convert data</td><td>Data conversion to a specific type failed, possibly due to format/content issues</td></tr><tr><td>10012</td><td>Can not initialize class</td><td>A dynamic class (such as handler, condition) can not be initialized (e.g. not available in current deployment)</td></tr><tr><td>10015</td><td>Missing id generator</td><td>Generator required for assigning new ids is not available</td></tr><tr><td>10016</td><td>Could not generate new id</td><td>Handler (e.g. write) failed to generate a new id to assign to current record</td></tr><tr><td>10019</td><td>Invalid update</td><td>Update request can not be applied to the current aggregate record</td></tr><tr><td>10024</td><td>Invalid condition json</td><td>Given json data can not be converted to a condition for filteration</td></tr><tr><td>10025</td><td>Event handler missing</td><td>Required handler by the event is not available on current runner</td></tr><tr><td>10026</td><td>Domain not defined</td><td>Handler requires domain data to be provided, which is missing in metadata </td></tr><tr><td>10027</td><td>Domain not available</td><td>Handler is asking for a domain (e.g. state) which is not available in current runner</td></tr><tr><td>10028</td><td>Missing aggregate</td><td>Required record for handler to function is missing in source state manager</td></tr><tr><td>10101</td><td>Failed to process command</td><td>Can not execute given command</td></tr><tr><td>10102</td><td>Failed to get file system</td><td>Can not initialize access to the file system for given name </td></tr><tr><td>10103</td><td>Unknown file system</td><td>File system referred to is not defined on this runner</td></tr><tr><td>10104</td><td>Could not create directory</td><td>File system failed to execute create directory command</td></tr><tr><td>10105</td><td>Could not delete</td><td>File system failed to execute delete command</td></tr><tr><td>10106</td><td>Could not rename</td><td>File system failed to execute rename command</td></tr><tr><td>10107</td><td>Could not list</td><td>File system failed to execute list files command</td></tr><tr><td>10108</td><td>Could not copy</td><td>File system failed to copy files</td></tr><tr><td>10109</td><td>Merge action timed out</td><td>Merge operation could not be completed before time out duration</td></tr><tr><td>10110</td><td>Merge step already processed</td><td>Given branch to merge into target is already processed</td></tr><tr><td>10111</td><td>Can not obtain merge lock</td><td>Failed to obtain a lock for merge operation</td></tr><tr><td>10112</td><td>Can not check merge status</td><td>Failed to check status of given merge operation from state manager</td></tr><tr><td>10113</td><td>Failed getting list</td><td>Handler (e.g. read) could not return the list of values required</td></tr><tr><td>10114</td><td>RestAPIEventHandler requires Restable runner</td><td>Rest handler is assigned to a runner which can not perform rest operations</td></tr><tr><td>10115</td><td>Can not produce headers</td><td>Rest handler failed to create request headers for the given event</td></tr><tr><td>10116</td><td>Can not initialize engine</td><td>Script handler failed to initialize engine for a specific language</td></tr><tr><td>10117</td><td>Failed to execute script/action</td><td>Script handler failed to execute script for the given event</td></tr><tr><td>10118</td><td>Paused event not found</td><td>Task handler could not find the record for continuing a given task</td></tr><tr><td>10119</td><td>Paused event already processed</td><td>Task handler already executed the given action on the target task (i.e. stale request)</td></tr><tr><td>10120</td><td>Paused event already timed out</td><td>Task to be proceeded timed out before proceed request is received</td></tr><tr><td>10121</td><td>Timeouts failed</td><td>Task handler failed to timeout tasks for a specific time period</td></tr><tr><td>10122</td><td>Can not apply transformation</td><td>Failed to transform given event data with a transformation class</td></tr><tr><td>10123</td><td>Missing token</td><td>Token required for authentication is missing in request.</td></tr><tr><td>10124</td><td>Expired token</td><td>Token provided for authentication already expired.</td></tr><tr><td>10125</td><td>Invalid token</td><td>Token provided for authentication is not valid (e.g. wrong format or contents).</td></tr><tr><td>10126</td><td>Can not hash password</td><td>Auth handler could not encode given password.</td></tr><tr><td>10127</td><td>Failed to evaluate condition</td><td>Failed to check a criteria on given event data with a condition class.</td></tr><tr><td>10128</td><td>Can not execute transaction</td><td>Transaction handler failed to execute given journals as a transaction.</td></tr><tr><td>10129</td><td>Failed to apply rules</td><td>Rule handler failed to execute rule logic on given event.</td></tr><tr><td>10130</td><td>Failed to run percolate query</td><td>Percolate handler failed to run query for a given event.</td></tr><tr><td>10131</td><td>Failed to score input</td><td>Model score handler failed to perform inference on provided event data.</td></tr><tr><td>10132</td><td>Failed to initialize model</td><td>Model score handler failed to initialize a specific data science model.</td></tr><tr><td>10133</td><td>Failed to execute python action</td><td>Python handler failed to execute a specific action using a Python module.</td></tr><tr><td>10134</td><td>No runtime for dataflow</td><td>CEP handler has no initialized runtimes for the requested dataflow. </td></tr><tr><td>10135</td><td>No handler for input</td><td>CEP handler has no activities defined for the given input stream. </td></tr><tr><td>10136</td><td>Failed to handle input</td><td>CEP handler failed to process given input data.</td></tr><tr><td>10137</td><td>Failed to persist apps</td><td>CEP handler failed to persist its current state in disk. </td></tr><tr><td>10138</td><td>Unknown function</td><td>Model score handler does not recognize given model inference function.</td></tr><tr><td>10139</td><td>Can not apply validation</td><td>Validation handler failed to apply validation check</td></tr><tr><td>10140</td><td>Path is not safe</td><td>Provided file system path contains resricted text (e.g. "..")</td></tr><tr><td>99999</td><td>Failed saga</td><td>Saga has failed, but the step with error did not provide any details.</td></tr></tbody></table>

In addition to these, rest related handlers also trigger error codes matching universal HTTP status codes (e.g. 400, 404) based on the target system response.

## State Errors

All state error codes start with "11", and are triggered by state runner elements.

<table><thead><tr><th width="100">Code</th><th width="271">Name</th><th width="385">Description</th></tr></thead><tbody><tr><td>11000</td><td>Invalid write request</td><td><a data-footnote-ref href="#user-content-fn-1">Write request is identified to be invalid but can not be categorized as stale, etc.</a></td></tr><tr><td>11001</td><td>Stale or jump write request</td><td><a data-footnote-ref href="#user-content-fn-2">Write request is either a repeated request or there is a missing update that should be applied first</a></td></tr><tr><td>11002</td><td>Stale write request</td><td>Current target record is already past the request's version or offset</td></tr><tr><td>11003</td><td>Jump write request</td><td>Write request is ahead of the current record version, there is missing update(s) in between</td></tr><tr><td>11004</td><td>Repated jump write request</td><td>A jump request is repeated multiple times, without filling the missing version updates</td></tr><tr><td>11005</td><td>Missing target</td><td>Record targered for an update is not available in the state manager (deleted or non-existing)</td></tr><tr><td>11006</td><td>Recreate request</td><td>Create request is sent for a record that already exists</td></tr><tr><td>11007</td><td>No undelete</td><td>State manager doesn't support undelete operations</td></tr><tr><td>11008</td><td>Wrong partition</td><td>Update request is received by a state manager not responsible for its partition</td></tr><tr><td>11009</td><td>Journal failed without exception</td><td>Update operation could not be applied, but there is no exception returned</td></tr><tr><td>11010</td><td>Unknown impact exception</td><td>Update operation could not be applied, and the returned exception is not from the expected list</td></tr><tr><td>11011</td><td>Can not initialize state manager</td><td>State manager failed to initialize, indicating possibly configuration issue </td></tr><tr><td>11012</td><td>State manager doesn't support feature</td><td>Update request asks for a feature that is not supported by this state manager</td></tr><tr><td>11013</td><td>Missing/invalid data schema</td><td>Validation data schema selected for the state manager is not available or properly formatted</td></tr><tr><td>11014</td><td>DDL failed</td><td>State manager failed to apply changes on its source table / collection</td></tr><tr><td>11015</td><td>Read failed</td><td>State manager failed to read requested record(s)</td></tr><tr><td>11016</td><td>State lock failure</td><td>State manager failed to perform lock for a concurrent operation</td></tr><tr><td>11103</td><td>State manager doesn't exist</td><td>Target state manager is not available within the current runner</td></tr><tr><td>11104</td><td>Manipulation failed</td><td>Aggregate manipulator used by the state manager failed to perform an operation</td></tr><tr><td>11105</td><td>External changes not allowed</td><td>State manager does not allow external changes, but received an uncontrolled update</td></tr><tr><td>11106</td><td>Mapping exception</td><td>Aggregate manipulator used by the state manager failed to map given data</td></tr><tr><td>11107</td><td>Mapper exception</td><td>Aggregate mapper used by the state manager failed to map given data</td></tr><tr><td>11201</td><td>Missing core state</td><td>Journal store manager is missing a core state manager for storing its records</td></tr><tr><td>11202</td><td>Core state is not a writable end state</td><td>Journal store manager's core state manager is not writeable</td></tr><tr><td>11203</td><td>Core state does not use journal data</td><td>Journal store manager's core state manager uses a data format different than journals</td></tr></tbody></table>

## Query Errors

All query error codes start with "12", and are triggered by query runner elements.

<table><thead><tr><th width="100">Code</th><th width="272">Name</th><th width="398">Description</th></tr></thead><tbody><tr><td>12001</td><td>Missing event parameters to build query</td><td>Query request event is missing required parameters for building the query</td></tr><tr><td>12002</td><td>Can not read query json</td><td>Json data passed as a query is missing or not in proper format</td></tr><tr><td>12003</td><td>Condition class not supported</td><td>Query manager does not support the condition type requested</td></tr><tr><td>12004</td><td>Local functions not supported</td><td>Query manager does not support use of local functions for operations</td></tr><tr><td>12005</td><td>Condition operator/join not supported</td><td>Query manager does not support given condition operator or join type</td></tr><tr><td>12006</td><td>LHS not compatible with condition type</td><td>Condition type requires a different data format than provided (e.g. single value vs array)</td></tr><tr><td>12008</td><td>Can not evaluate custom/command</td><td>Provided command can not be translated into target query manager's language</td></tr><tr><td>12007</td><td>Ided functions not supported</td><td>Query manager does not support use of stored functions for operations</td></tr><tr><td>12009</td><td>Query failed</td><td>Query execution failed at target system</td></tr><tr><td>12010</td><td>Query class not supported</td><td>Query manager does not support the query type requested</td></tr><tr><td>12011</td><td>Can not convert condition</td><td>Provided condition definitioncan not be converted to a proper condition format</td></tr><tr><td>12012</td><td>Can not convert query</td><td>Provided query definition can not be converted to a proper query format</td></tr><tr><td>12013</td><td>Query function not supported</td><td>Requested function is not supported by the target query manager</td></tr><tr><td>12014</td><td>Can not set query property</td><td>Failed to set the given property for query</td></tr></tbody></table>

## Runner Errors

All runner error codes start with "13", and are triggered by runners themselves.

<table><thead><tr><th width="100">Code</th><th width="244">Name</th><th width="423">Description</th></tr></thead><tbody><tr><td>13001</td><td>Can not rebuild runner</td><td>Rebuild command has failed for the runner</td></tr><tr><td>13002</td><td>Can not stop runner</td><td>Stop command has failed for the runner</td></tr><tr><td>13003</td><td>Can not pause runner</td><td>Pause command has failed for the runner</td></tr><tr><td>13004</td><td>Missing command parameter</td><td>Command received by the runner is missing a required parameter</td></tr><tr><td>13005</td><td>Can not commit</td><td>Commit command has failed for the runner</td></tr><tr><td>13006</td><td>Reconnect failed</td><td>Runner failed to reconnect to a target system (e.g. database, file system)</td></tr><tr><td>13010</td><td>Failed to find handler for local call</td><td>Runner is missing the required handler for making a local event call</td></tr><tr><td>13011</td><td>Only events are allowed on local stream</td><td>Runner received data other than an event for a local event call</td></tr><tr><td>13020</td><td>Failed delivery</td><td>Runner failed to send a message to a target system (e.g. Kafka)</td></tr><tr><td>13021</td><td>Partition logic issue</td><td>Multiple partitions of the same stream is assigned to a single instance of the runner</td></tr><tr><td>13022</td><td>Wrong runner type</td><td>Runner is deployed using a wrong runner class</td></tr><tr><td>13101</td><td>Failed to get file system</td><td>Can not configure access to a given file system</td></tr><tr><td>13102</td><td>Failed to extract files</td><td>Can not extract contents of a compressed file</td></tr><tr><td>13103</td><td>Failed to compress files</td><td>Can not compress given files</td></tr><tr><td>13104</td><td>Failed to delete remote folder</td><td>Can not delete a folder on given file system</td></tr><tr><td>13105</td><td>Failed to copy to local</td><td>Can not copy from a given file system to local directory</td></tr><tr><td>13106</td><td>Failed to copy to remote</td><td>Can not copy to a given file system from local directory</td></tr><tr><td>13107</td><td>Failed to upload file</td><td>Can not upload received file to a given file system</td></tr><tr><td>13108</td><td>Failed to download file</td><td>Can not download requested file from a given file system</td></tr><tr><td>13109</td><td>Failed to get file status</td><td>Can not get file status details from the given file system</td></tr><tr><td>13110</td><td>Failed to delete</td><td>Can not delete a file on given file system</td></tr><tr><td>13111</td><td>Failed to rename</td><td>Can not rename a file/folder on given file system</td></tr><tr><td>13112</td><td>Failed to list files</td><td>Can not list files on a given file system</td></tr><tr><td>13113</td><td>Failed to create dir</td><td>Can not create a new folder on a given file system</td></tr><tr><td>13201</td><td>Can not convert response to event</td><td>Rest operation failed to convert received response into event data format</td></tr><tr><td>13202</td><td>Can not initialize trusting rest client</td><td>Rest operation failed to initialize a new client trusting https connections</td></tr><tr><td>13203</td><td>Can not prepare xml body</td><td>Rest operation failed to prepare XML body from provided data</td></tr><tr><td>13204</td><td>Can not process response body</td><td>Rest operation failed to process received response contents</td></tr><tr><td>13205</td><td>Can not initialize auth service</td><td>Rest operation failed to initialize authentication services for connections</td></tr><tr><td>13206</td><td>Can not issue token with credentials</td><td>Rest operation failed to issue a token for connection to target system</td></tr><tr><td>13207</td><td>Grant type not supported</td><td>Rest operation does not support token grant type requested</td></tr></tbody></table>

In addition to these, rest related runners also trigger error codes matching universal HTTP status codes (e.g. 400, 404) based on the target system response.

## Saga Errors

Saga event handler uses its own set of errors, in addition to standard handler error codes.

<table><thead><tr><th width="68">Code</th><th width="219.66972477064218">Name</th><th width="461">Description</th></tr></thead><tbody><tr><td>1</td><td>Saga timed out</td><td>Saga failed to return before timeout duration</td></tr><tr><td>3</td><td>No active saga for path</td><td>Requested path does not have an active saga associated with it</td></tr><tr><td>6</td><td>Missing step for saga</td><td>Saga is missing the requested step id in its design and can not continue</td></tr><tr><td>11</td><td>Saga in open state</td><td>Circuit breaker put requested saga in open state, hence it is not accepting new requests</td></tr><tr><td>12</td><td>Unknown step type</td><td>Next step for the request is not of a standard saga step type</td></tr><tr><td>13</td><td>Payload not matching Json schema</td><td>Saga has a specific input schema and the received request payload does not match this schema</td></tr><tr><td>14</td><td>User does not have required roles</td><td>Saga requires a specific set of roles for access and the current user does not have any of these roles</td></tr></tbody></table>

## Gateway Errors

All gateway error codes start with "17", and are triggered by API gateways themselves.

<table><thead><tr><th width="100">Code</th><th width="261.5652173913043">Name</th><th width="389">Description</th></tr></thead><tbody><tr><td>17001</td><td>Failed to load/refresh configuration</td><td>Gateway can not update its configuration (e.g. for channels)</td></tr><tr><td>17002</td><td>No configuration exists</td><td>Gateway does not have a configuration defined for the requested id</td></tr><tr><td>17003</td><td>Failed to initialize service/token</td><td>Gateway failed to load and initialize a service or token </td></tr><tr><td>17004</td><td>Refresh level is not supported</td><td>Gateway does not support refresh of the configuration at requested level</td></tr><tr><td>17005</td><td>Kafka system not found</td><td>Requested Kafka system is not available on current gateway</td></tr><tr><td>17006</td><td>Feature not enabled</td><td>Gateway does not allow using requested feature (e.g. sending commands)</td></tr><tr><td>17007</td><td>Unknown command</td><td>Gateway received a control command which is not recognized</td></tr><tr><td>17008</td><td>File system not found</td><td>Gateway received request for a file system not configured for access</td></tr><tr><td>17009</td><td>Invalid file path</td><td>Gateway received request on a file system with invalid file path</td></tr><tr><td>17010</td><td>Failed to perform file operation</td><td>Gateway failed to perform requested operation on a file system</td></tr><tr><td>17011</td><td>Failed to parse response</td><td>Gateway failed to parse response received from a microservice</td></tr></tbody></table>

[^1]: Only returned by state manager implementations that can not identify root cause

[^2]: Only returned by state manager implementations that can not identify the difference


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.rierino.com/troubleshooting/error-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.