You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support appliances that are in a starting state, or are offline (down).
Currently the bot will not start until a connection is established, and will fail on subsequent calls if the apliance goes down.
Currently, if you send a REST call to an appliance that is starting, you get:
$ curl -k https://16.125.73.152/rest/status/starting
{"errorSource":null,"nestedErrors":[],"errorCode":"ERR_CONTROLLER_STARTING","data":{},"recommendedActions":["Wait for the appliance to complete its startup, then resend the request."],"details":"Requests cannot be serviced while the appliance is starting up.","message":"The appliance is starting."}
This could be detected by the bot.
The text was updated successfully, but these errors were encountered:
Support appliances that are in a starting state, or are offline (down).
Currently the bot will not start until a connection is established, and will fail on subsequent calls if the apliance goes down.
Currently, if you send a REST call to an appliance that is starting, you get:
$ curl -k https://16.125.73.152/rest/status/starting
{"errorSource":null,"nestedErrors":[],"errorCode":"ERR_CONTROLLER_STARTING","data":{},"recommendedActions":["Wait for the appliance to complete its startup, then resend the request."],"details":"Requests cannot be serviced while the appliance is starting up.","message":"The appliance is starting."}
This could be detected by the bot.
The text was updated successfully, but these errors were encountered: