Error Codes
System errors are returned with codes and payload details
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.
10001
Action/role not supported
Handler does not support the requested action or role
10002
Event version not supported
Handler does not support the requested event version
10004
Failed to generate id
Id generator failed to produce a new id
10005
Can not clear cache
Cacheable handler failed to clear its cache (e.g. on command)
10006
Input element not defined
Request event is missing input payload on given input element path
10008
Missing input payload
Request event is missing input payload on given input element path
10009
Missing parameter
Request event is missing a mandatory metadata parameter
10010
If pattern failed for edit
Edit action has a validity condition which current request fails to meet
10011
Can not convert data
Data conversion to a specific type failed, possibly due to format/content issues
10012
Can not initialize class
A dynamic class (such as handler, condition) can not be initialized (e.g. not available in current deployment)
10015
Missing id generator
Generator required for assigning new ids is not available
10016
Could not generate new id
Handler (e.g. write) failed to generate a new id to assign to current record
10019
Invalid update
Update request can not be applied to the current aggregate record
10024
Invalid condition json
Given json data can not be converted to a condition for filteration
10025
Event handler missing
Required handler by the event is not available on current runner
10026
Domain not defined
Handler requires domain data to be provided, which is missing in metadata
10027
Domain not available
Handler is asking for a domain (e.g. state) which is not available in current runner
10028
Missing aggregate
Required record for handler to function is missing in source state manager
10101
Failed to process command
Can not execute given command
10102
Failed to get file system
Can not initialize access to the file system for given name
10103
Unknown file system
File system referred to is not defined on this runner
10104
Could not create directory
File system failed to execute create directory command
10105
Could not delete
File system failed to execute delete command
10106
Could not rename
File system failed to execute rename command
10107
Could not list
File system failed to execute list files command
10108
Could not copy
File system failed to copy files
10109
Merge action timed out
Merge operation could not be completed before time out duration
10110
Merge step already processed
Given branch to merge into target is already processed
10111
Can not obtain merge lock
Failed to obtain a lock for merge operation
10112
Can not check merge status
Failed to check status of given merge operation from state manager
10113
Failed getting list
Handler (e.g. read) could not return the list of values required
10114
RestAPIEventHandler requires Restable runner
Rest handler is assigned to a runner which can not perform rest operations
10115
Can not produce headers
Rest handler failed to create request headers for the given event
10116
Can not initialize engine
Script handler failed to initialize engine for a specific language
10117
Failed to execute script/action
Script handler failed to execute script for the given event
10118
Paused event not found
Task handler could not find the record for continuing a given task
10119
Paused event already processed
Task handler already executed the given action on the target task (i.e. stale request)
10120
Paused event already timed out
Task to be proceeded timed out before proceed request is received
10121
Timeouts failed
Task handler failed to timeout tasks for a specific time period
10122
Can not apply transformation
Failed to transform given event data with a transformation class
10123
Missing token
Token required for authentication is missing in request.
10124
Expired token
Token provided for authentication already expired.
10125
Invalid token
Token provided for authentication is not valid (e.g. wrong format or contents).
10126
Can not hash password
Auth handler could not encode given password.
10127
Failed to evaluate condition
Failed to check a criteria on given event data with a condition class.
10128
Can not execute transaction
Transaction handler failed to execute given journals as a transaction.
10129
Failed to apply rules
Rule handler failed to execute rule logic on given event.
10130
Failed to run percolate query
Percolate handler failed to run query for a given event.
10131
Failed to score input
Model score handler failed to perform inference on provided event data.
10132
Failed to initialize model
Model score handler failed to initialize a specific data science model.
10133
Failed to execute python action
Python handler failed to execute a specific action using a Python module.
10134
No runtime for dataflow
CEP handler has no initialized runtimes for the requested dataflow.
10135
No handler for input
CEP handler has no activities defined for the given input stream.
10136
Failed to handle input
CEP handler failed to process given input data.
10137
Failed to persist apps
CEP handler failed to persist its current state in disk.
10138
Unknown function
Model score handler does not recognize given model inference function.
10139
Can not apply validation
Validation handler failed to apply validation check
10140
Path is not safe
Provided file system path contains resricted text (e.g. "..")
99999
Failed saga
Saga has failed, but the step with error did not provide any details.
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.
11000
Invalid write request
11001
Stale or jump write request
11002
Stale write request
Current target record is already past the request's version or offset
11003
Jump write request
Write request is ahead of the current record version, there is missing update(s) in between
11004
Repated jump write request
A jump request is repeated multiple times, without filling the missing version updates
11005
Missing target
Record targered for an update is not available in the state manager (deleted or non-existing)
11006
Recreate request
Create request is sent for a record that already exists
11007
No undelete
State manager doesn't support undelete operations
11008
Wrong partition
Update request is received by a state manager not responsible for its partition
11009
Journal failed without exception
Update operation could not be applied, but there is no exception returned
11010
Unknown impact exception
Update operation could not be applied, and the returned exception is not from the expected list
11011
Can not initialize state manager
State manager failed to initialize, indicating possibly configuration issue
11012
State manager doesn't support feature
Update request asks for a feature that is not supported by this state manager
11013
Missing/invalid data schema
Validation data schema selected for the state manager is not available or properly formatted
11014
DDL failed
State manager failed to apply changes on its source table / collection
11015
Read failed
State manager failed to read requested record(s)
11016
State lock failure
State manager failed to perform lock for a concurrent operation
11103
State manager doesn't exist
Target state manager is not available within the current runner
11104
Manipulation failed
Aggregate manipulator used by the state manager failed to perform an operation
11105
External changes not allowed
State manager does not allow external changes, but received an uncontrolled update
11106
Mapping exception
Aggregate manipulator used by the state manager failed to map given data
11107
Mapper exception
Aggregate mapper used by the state manager failed to map given data
11201
Missing core state
Journal store manager is missing a core state manager for storing its records
11202
Core state is not a writable end state
Journal store manager's core state manager is not writeable
11203
Core state does not use journal data
Journal store manager's core state manager uses a data format different than journals
Query Errors
All query error codes start with "12", and are triggered by query runner elements.
12001
Missing event parameters to build query
Query request event is missing required parameters for building the query
12002
Can not read query json
Json data passed as a query is missing or not in proper format
12003
Condition class not supported
Query manager does not support the condition type requested
12004
Local functions not supported
Query manager does not support use of local functions for operations
12005
Condition operator/join not supported
Query manager does not support given condition operator or join type
12006
LHS not compatible with condition type
Condition type requires a different data format than provided (e.g. single value vs array)
12008
Can not evaluate custom/command
Provided command can not be translated into target query manager's language
12007
Ided functions not supported
Query manager does not support use of stored functions for operations
12009
Query failed
Query execution failed at target system
12010
Query class not supported
Query manager does not support the query type requested
12011
Can not convert condition
Provided condition definitioncan not be converted to a proper condition format
12012
Can not convert query
Provided query definition can not be converted to a proper query format
12013
Query function not supported
Requested function is not supported by the target query manager
12014
Can not set query property
Failed to set the given property for query
Runner Errors
All runner error codes start with "13", and are triggered by runners themselves.
13001
Can not rebuild runner
Rebuild command has failed for the runner
13002
Can not stop runner
Stop command has failed for the runner
13003
Can not pause runner
Pause command has failed for the runner
13004
Missing command parameter
Command received by the runner is missing a required parameter
13005
Can not commit
Commit command has failed for the runner
13006
Reconnect failed
Runner failed to reconnect to a target system (e.g. database, file system)
13010
Failed to find handler for local call
Runner is missing the required handler for making a local event call
13011
Only events are allowed on local stream
Runner received data other than an event for a local event call
13020
Failed delivery
Runner failed to send a message to a target system (e.g. Kafka)
13021
Partition logic issue
Multiple partitions of the same stream is assigned to a single instance of the runner
13022
Wrong runner type
Runner is deployed using a wrong runner class
13101
Failed to get file system
Can not configure access to a given file system
13102
Failed to extract files
Can not extract contents of a compressed file
13103
Failed to compress files
Can not compress given files
13104
Failed to delete remote folder
Can not delete a folder on given file system
13105
Failed to copy to local
Can not copy from a given file system to local directory
13106
Failed to copy to remote
Can not copy to a given file system from local directory
13107
Failed to upload file
Can not upload received file to a given file system
13108
Failed to download file
Can not download requested file from a given file system
13109
Failed to get file status
Can not get file status details from the given file system
13110
Failed to delete
Can not delete a file on given file system
13111
Failed to rename
Can not rename a file/folder on given file system
13112
Failed to list files
Can not list files on a given file system
13113
Failed to create dir
Can not create a new folder on a given file system
13201
Can not convert response to event
Rest operation failed to convert received response into event data format
13202
Can not initialize trusting rest client
Rest operation failed to initialize a new client trusting https connections
13203
Can not prepare xml body
Rest operation failed to prepare XML body from provided data
13204
Can not process response body
Rest operation failed to process received response contents
13205
Can not initialize auth service
Rest operation failed to initialize authentication services for connections
13206
Can not issue token with credentials
Rest operation failed to issue a token for connection to target system
13207
Grant type not supported
Rest operation does not support token grant type requested
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.
1
Saga timed out
Saga failed to return before timeout duration
3
No active saga for path
Requested path does not have an active saga associated with it
6
Missing step for saga
Saga is missing the requested step id in its design and can not continue
11
Saga in open state
Circuit breaker put requested saga in open state, hence it is not accepting new requests
12
Unknown step type
Next step for the request is not of a standard saga step type
13
Payload not matching Json schema
Saga has a specific input schema and the received request payload does not match this schema
14
User does not have required roles
Saga requires a specific set of roles for access and the current user does not have any of these roles
Gateway Errors
All gateway error codes start with "17", and are triggered by API gateways themselves.
17001
Failed to load/refresh configuration
Gateway can not update its configuration (e.g. for channels)
17002
No configuration exists
Gateway does not have a configuration defined for the requested id
17003
Failed to initialize service/token
Gateway failed to load and initialize a service or token
17004
Refresh level is not supported
Gateway does not support refresh of the configuration at requested level
17005
Kafka system not found
Requested Kafka system is not available on current gateway
17006
Feature not enabled
Gateway does not allow using requested feature (e.g. sending commands)
17007
Unknown command
Gateway received a control command which is not recognized
17008
File system not found
Gateway received request for a file system not configured for access
17009
Invalid file path
Gateway received request on a file system with invalid file path
17010
Failed to perform file operation
Gateway failed to perform requested operation on a file system
17011
Failed to parse response
Gateway failed to parse response received from a microservice
Last updated