Recovering from EIS Errors

After sending a JSON request to Unwired Server, if you receive in the response log message an EIS code which is recoverable, the mobile workflow client throws a TransformRetryException or ResponseRetryException, as is appropriate.

A retry attempt is made after a retry time interval, which is set by default to 15 minutes for recoverable errors, and by default to 3 days for unrecoverable errors. You can configure the retry time interval by setting the SupRecoverableErrorRetryTimeout (default: 15 minutes) and SupUnrecoverableErrorRetryTimeout context variables through the Sybase Control Center admin console.

Only certain error codes are considered to be recoverable.

Recoverable Error Codes
Error Code Probable Cause
409 Backend EIS is deadlocked.
503 Backend EIS down or the connection is terminated.
Note: If the problem with the EIS is not corrected, the retry process can continue indefinitely. Ensure that you set an appropriate retry time interval.

Other error codes are considered to be non-recoverable. A retry attempt is made after a retry time interval, which is set to three days by default.

Non-recoverable Error Codes
Error Code Probable Cause Manual Recovery Action
401 Backend EIS credentials wrong. Change the connection information, or backend user password.
403 User authorization failed on Unwired Server due to role constraints (applicable only for MBS). N/A
404 Resource (table/webservice/BAPI) not found on Backend EIS. Restore the EIS configuration.
405 Invalid license for the client (applicable only for MBS). N/A
412 Backend EIS threw a constraint exception. Delete the conflicting entry in the EIS.
500 SUP internal error in modifying the CDB cache. N/A
Related concepts
HTTP Error Codes
Mapping of EIS Codes to Logical HTTP Error Codes
Credentials Are Lost after User Successfully Passes Activation Screen
Related tasks
Configuring Context Variables for Mobile Workflow Packages
Related reference
Mobile Workflow Exception Handling
Unable to Deploy Workflow