Google Drive Extension Error Codes

All-in-One WP Migration Google Drive extension error codes information

Please find below details about error codes Google Drive extension API server may

Code: 400 ‘Bad Request’
User error. This can mean that a required field or parameter has not been provided, the value supplied is invalid, or the combination of provided fields is invalid.
This error can be thrown when trying to add a duplicate parent to a Drive item. It can also be thrown when trying to add a parent that would create a cycle in the directory graph.

Code: 401 ‘Unauthorized’
Invalid authorization header. The access token you’re using is either expired or invalid. Suggested action: Refresh the access token using the long-lived refresh token.

Code: 402 ‘Payment Required’
Payment for the product is required in order to proceed.

Code: 403 ‘Forbidden’
Forbidden access. The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.

Error: ‘Daily Limit Exceeded’
The Courtesy API limit for your project has been reached. Suggested action: Request additional quota.

Error: ‘User Rate Limit Exceeded’
The per-user limit has been reached. This may be the limit from the Developer Console or a limit from the Drive backend.

Error: Rate Limit Exceeded
The user has reached Google Drive API’s maximum request rate. The limit varies depending on the kind of requests.

Error: Sharing Rate Limit Exceeded
The user has reached a sharing limit. This is often linked with an email limit.
Suggested actions:
– Do not send emails when sharing lot of files.
– If one user is making a lot of requests on behalf of many users of a G Suite domain, consider a Service Account with authority delegation to impersonate the owner of each document to share.

Error: The user has not granted the app ‘App ID’ access to the file ‘File ID’
The requesting app is not on the ACL for the file. The user never explicitly opened the file with this Drive app.

Error: The user does not have sufficient permissions for file ‘File ID’
The user does not have write access to a file, and the app is attempting to modify that file.
Suggested action: Report to the user that there is a need to ask for those permissions in order to update the file.

Error: App with id ‘App ID’ cannot be used within the authenticated user’s domain
The policy for the user’s domain does not allow access to Google Drive by your app.
Suggested action: Report to the user that the domain does not allow your app to access files in Drive.

Code: 404 ‘Not Found’
The user does not have read access to a file, or the file does not exist. Suggested action: Report to users that they do not have read access to the file or that the file does not exist. Tell them that they should ask the owner for permission to the file.

Code: 405 ‘Method Not Allowed’
The HTTP method in the request is not allowed on the resource.

Code: 406 ‘Not Acceptable’
This service doesn’t support the format requested in the Accept header. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

Code: 407 ‘Proxy Authentication Required’
Proxy authentication required. The client must first authenticate themselves with the proxy.

Code: 408 ‘Request Timeout’
Request timed out. The server timed out waiting for the request. The client did not produce a request within the time that the server was prepared to wait. Repeat the request without modifications at any later time.

Code: 409 ‘Conflict’
The current state conflicts with what the request expects. Request could not be processed because of the conflict.

Code: 410 ‘Gone’
The requested resource is no longer available at the server.

Code: 411 ”Length Required’
A Content-Length based header is required on the request.

Code: 412 ‘Precondition Failed’
The server does not meet one of the preconditions that the requester put on the request.

Code 413 ‘Request Entity Too Large’
The request size exceeds maximum limit.

Code 414 ‘Request-URI Too Long’
Request-URI too long. The URI provided was too long for the server to process.

Code: 415 ‘Unsupported Media Type’
The content type of the request is a format that is not supported by the service.

Code: 416 ‘Requested Range Not Satisfiable’
The specified byte range is invalid or unavailable.

Code: 417 ‘Expectation Failed’
Expectation failed. The server cannot meet the requirements of the Expect request-header field.

Code: 429 ‘Too Many Requests’
The user has sent too many requests in a given amount of time.

Code: 500 ‘Internal Server Error’
An unexpected error occurred while processing the request.

Code: 501 ‘Not Implemented’
The requested feature is not implemented.

Code: 502 ‘Bad Gateway’
Bad gateway. The server was acting as a gateway or a proxy and received an invalid response from the upstream server.

Code: 503 ‘Service Unavailable’
The service is temporarily unavailable. You may repeat the request after a delay. There may be a Retry-After header.

Code: 504 ‘Gateway Timeout’
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

Code: 505 ‘HTTP Version Not Supported’
The server does not support the HTTP protocol version used in the request.

Leave A Comment?