Common Errors

this guide describes the reasons why functions fail, and a complete list of errors that can occur when running functions when a function is executed and an error occurs, an error message is displayed unauthorized request or token expired an "errors" message is displayed during any operation if the request is unauthorized or the token is expired { "errors" \[ { "errortype" "unauthorizedexception", "message" "token has expired " } ] } deprecated field an error with errortype "deprecated" will be returned if a field which is present in the query or mutation has been deprecated this field will be removed at a future point in time the query or mutation should be altered so that this field is no longer used the message portion of the error will specify the reason for the deprecation and, where relevant, an alternative field to use the response payload remains valid and is safe to consume { "errors" \[ { "errortype" "deprecated", "message" "query organization is deprecated, use organizationidsearch instead" } ] } all deprecated fields will eventually be removed from the api schema whilst receiving a deprecated error is not fatal, it does indicate that your query will fail at a future point in time and must be adjusted unknown issue the following the following error message is shown in case of an unknown issue "errormessage" "unknown error occurred during request please contact support providing following error id 7232cf38 f3c9 40d8 80c9 5b9400bf2bc1" typo if you mistype the name of a field or query, an error displays when you try to run the query { "data" null, "errors" \[ { "path" null, "locations" \[ { "line" 2, "column" 5, "sourcename" null } ], "message" "validation error of type fieldundefined field 'list' in type 'query' is undefined @ 'list'" } ] }