Error Handling

If there are abnormal situations, SAP SSC cloud edition informs the calling application or user with adequate HTTP error code as listed in the below table. In case SSC engine is invoked by SSC UI , then those error codes are also translated into more meaningful detailed messages for easier understanding:


HTTP Error Code	Error Description	SSC Configuration Interface message
401	Authorization error	Unauthorized
403	Forbidden error	Forbidden
404	Not found	Not Found
429	Too Many Requests	Too Many Requests. retry after some time.
500	Internal server error	A server error has occurred for this configuration, contact your system administrator.
501	Not Implemented	A server error has occurred for this configuration, contact your system administrator.
502	Bad Gateway	A server error has occurred. Click OK to reload the UI or Cancel to start again. If the problem persists, contact your system administrator.
503	Service Unavailable	A server error has occurred. Click OK to reload the UI or Cancel to start again. If the problem persists, contact your system administrator.
504	Gateway Timeout	A server error has occurred. Click OK to reload the UI or Cancel to start again. If the problem persists, contact your system administrator.

Timeouts

A configuration session is kept alive for 30 min of idle time by SSC Configuration UI. Also if there are executions of long configuration steps in engine, the session is kept alive for about 2-minutes post which HTTP status 504 is received by the UI. Modelers must test thoroughly to ensure that the configuration steps do not take more than 2-minutes of execution time in worst case scenario; else, the end users cannot execute these configuration steps.