The Google Drive API returns two levels of error information:
- HTTP error codes and header messages.
- A JSON object in the response body with additional details that can help you determine how to handle the error.
Google Drive apps should catch and handle all errors that might be encountered when using the REST API. This guide provides instructions about how to resolve specific Drive API errors.
HTTP status code summary
| Error code | Description |
|---|---|
200 - OK
|
The request is successful (this is the standard response for successful HTTP requests). |
400 - Bad Request
|
The request cannot be fulfilled due to a client error in the request. |
401 - Unauthorized
|
The request contains invalid credentials. |
403 - Forbidden
|
The request was received and understood, but the user doesn't have permission to perform the request. |
404 - Not Found
|
The requested page couldn't be found. |
429 - Too Many Requests
|
Too many requests to the API. |
500, 502, 503, 504 - Server Errors
|
Unexpected error arises while processing the request. |
400 errors
These errors mean that the request was unacceptable, often due to a missing required parameter.
badRequest
This error can occur from any one of the following issues in your code:
- A required field or parameter hasn't been provided.
- The value supplied or a combination of provided fields is invalid.
- You tried to add a duplicate parent to a Drive file.
- You tried to add a parent that would create a cycle in the directory graph.
The following JSON sample is a representation of this error:
{
" error
" :
{
" code
" :
400
,
" errors
" :
[
{
" domai
n
" :
" global
" ,
" loca
t
io
n
" :
" orderBy
" ,
" loca
t
io
n
Type
" :
" parame
ter
" ,
" message
" :
" Sor
t
i
n
g
is
n
o
t
suppor
te
d
f
or
queries
wi
t
h
full
Tex
t
ter
ms.
Resul
ts
are
always
i
n
desce
n
di
n
g
releva
n
ce
order.
" ,
" reaso
n
" :
" badReques
t
"
}
],
" message
" :
" Sor
t
i
n
g
is
n
o
t
suppor
te
d
f
or
queries
wi
t
h
full
Tex
t
ter
ms.
Resul
ts
are
always
i
n
desce
n
di
n
g
releva
n
ce
order.
"
}
}
To fix this error, check the message
field and adjust your code accordingly.
invalidSharingRequest
This error occurs for several reasons. To determine the cause, evaluate the reason
field of the returned JSON. This error most commonly occurs because:
- Sharing succeeded, but the notification email wasn't correctly delivered.
- The Access Control List (ACL) change isn't allowed for this user.
The message
field indicates the actual error.
Share succeeded, but the notification email wasn't correctly delivered
The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" i
n
validShari
n
gReques
t
" ,
" message
" :
" Bad
Reques
t
.
User
message
:
\"Sorry
,
t
he
i
te
ms
were
success
full
y
shared
bu
t
emails
could
n
o
t
be
se
nt
t
o
email@domai
n
.com.\
""
}
],
" code
" :
400
,
" message
" :
" Bad
Reques
t
"
}
}
To fix this error, inform the user (sharer) they were unable to share because the notification email couldn't be sent to the destination email address. The user should make sure they have the correct email address and that it can receive email.
The ACL change isn't allowed for this user
The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" i
n
validShari
n
gReques
t
" ,
" message
" :
" Bad
Reques
t
.
User
message
:
\"ACL
cha
n
ge
n
o
t
allowed.\
""
}
],
" code
" :
400
,
" message
" :
" Bad
Reques
t
"
}
}
To fix this error, check the sharing settings of the Google Workspace domain to which the file belongs. The settings might prohibit sharing outside of the domain or sharing a shared drive might not be permitted.
401 errors
These errors mean the request doesn't contain a valid access token.
authError
This error occurs when the access token that you're using is either expired or invalid. This error can also be caused by missing authorization for the requested scopes. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" au
t
hError
" ,
" message
" :
" I
n
valid
Crede
nt
ials
" ,
" loca
t
io
n
Type
" :
" header
" ,
" loca
t
io
n
" :
" Au
t
horiza
t
io
n
" ,
}
],
" code
" :
401
,
" message
" :
" I
n
valid
Crede
nt
ials
"
}
}
To fix this error, refresh the access token using the long-lived refresh token. If this fails, direct the user through the OAuth flow, as described in Choose Google Drive API scopes .
fileNotDownloadable
This error occurs when you try to use the revisions.get
method with the alt=media
URL parameter on a Google Workspace document. The following JSON
sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" f
ileNo
t
Dow
nl
oadable
" ,
" message
" :
" O
nl
y
f
iles
wi
t
h
bi
nar
y
co
ntent
ca
n
be
dow
nl
oaded.
Use
Expor
t
wi
t
h
Docs
Edi
t
ors
f
iles.
"
}
],
" code
" :
403
,
" message
" :
" O
nl
y
f
iles
wi
t
h
bi
nar
y
co
ntent
ca
n
be
dow
nl
oaded.
Use
Expor
t
wi
t
h
Docs
Edi
t
ors
f
iles.
"
}
}
To fix this error, try any of the following:
- Remove the
alt=mediaURL parameter if you want to view the metadata of a particular revision, such as the mimetype. - Use the
files.exportmethod to export Google Workspace document byte content. For more information, see Export Google Workspace document content .
403 errors
These errors mean that a usage limit has been exceeded or the user doesn't have
the correct privileges. To determine the cause, evaluate the reason
field of
the returned JSON.
For information about Drive API limits, refer to Usage limits . For information about Drive folder limits, refer to File and folder limits .
activeItemCreationLimitExceeded
An activeItemCreationLimitExceeded
error occurs when the limit for the number
of items created per account has been exceeded. Each user can have up to 500
million items created by an account. For more information, see User-item
limit
.
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" ac
t
iveI
te
mCrea
t
io
n
Limi
t
Exceeded
" ,
" message
" :
" This
accou
nt
has
exceeded
t
he
crea
t
io
n
limi
t
o
f
500
millio
n
i
te
ms.
To
crea
te
more
i
te
ms
,
perma
nentl
y
dele
te
some
i
te
ms.
"
}
],
" code
" :
403
,
" message
" :
" This
accou
nt
has
exceeded
t
he
crea
t
io
n
limi
t
o
f
500
millio
n
i
te
ms.
To
crea
te
more
i
te
ms
,
perma
nentl
y
dele
te
some
i
te
ms.
"
}
}
To fix this error:
-
Inform the user that Drive prevents accounts from creating more than 500 million items.
-
If the user must create items in this same account, instruct them to permanently delete some objects. Otherwise, they can use a different account that already meets the requirement.
appNotAuthorizedToFile
This error occurs when your app isn't on the ACL for the file. This error prevents the user from opening the file with your app. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" appNo
t
Au
t
horizedToFile
" ,
" message
" :
" The
user
has
n
o
t
gra
nte
d
t
he
app
{
appId
}
{
verb
}
access
t
o
t
he
f
ile
{
f
ileId
}
.
"
}
],
" code
" :
403
,
" message
" :
" The
user
has
n
o
t
gra
nte
d
t
he
app
{
appId
}
{
verb
}
access
t
o
t
he
f
ile
{
f
ileId
}
.
"
}
}
To fix this error, try any of the following:
- Open the Google Drive picker and prompt the user to open the file.
- Instruct the user to open the file using the Open with context menu in the Drive UI of your app.
- Use the
files.getmethod to check theisAppAuthorizedfield on thefilesresource to verify that your app created or opened the file.
cannotModifyInheritedTeamDrivePermission
This error occurs when a user tries to modify the inherited permissions of an item within a shared drive. Inherited permissions can't be removed from an item in a shared drive. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" ca
nn
o
t
Modi
f
yI
n
heri
te
dTeamDrivePermissio
n
" ,
" message
" :
" Ca
nn
o
t
upda
te
or
dele
te
a
n
i
n
heri
te
d
permissio
n
o
n
a
shared
drive
i
te
m.
"
}
],
" code
" :
403
,
" message
" :
" Ca
nn
o
t
upda
te
or
dele
te
a
n
i
n
heri
te
d
permissio
n
o
n
a
shared
drive
i
te
m.
"
}
}
To fix this error, a user must adjust the permissions on the direct or indirect
parent item from which they were inherited. For more information, see Permission
propagation
. You can
also retrieve the permissions.permissionDetails
resource to see whether the permissions on this shared drive item are inherited
or applied directly.
dailyLimitExceeded
This error occurs when the API limit for your project was reached. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" usageLimi
ts
" ,
" reaso
n
" :
" dailyLimi
t
Exceeded
" ,
" message
" :
" Daily
Limi
t
Exceeded
"
}
],
" code
" :
403
,
" message
" :
" Daily
Limi
t
Exceeded
"
}
}
This error appears when the application's owner has set a quota limit to cap usage of a particular resource. To fix this error, remove any usage caps for the "Queries per day" quota .
domainPolicy
This error occurs when the policy for the user's domain doesn't allow access to Drive by your app. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" domai
n
Policy
" ,
" message
" :
" The
domai
n
admi
n
is
trat
ors
have
disabled
Drive
apps.
"
}
],
" code
" :
403
,
" message
" :
" The
domai
n
admi
n
is
trat
ors
have
disabled
Drive
apps.
"
}
}
To fix this error:
- Inform the user that the domain doesn't allow your app to access files in Drive.
- Instruct the user to contact the domain administrator to request access for your app.
fileOwnerNotMemberOfTeamDrive
This error occurs when attempting to move a file into a shared drive and the file owner isn't a member. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" f
ileOw
ner
No
t
MemberO
f
TeamDrive
" ,
" message
" :
" Ca
nn
o
t
move
a
f
ile
i
nt
o
a
shared
drive
as
a
wri
ter
whe
n
t
he
ow
ner
o
f
t
he
f
ile
is
n
o
t
a
member
o
f
t
ha
t
shared
drive.
"
}
],
" code
" :
403
,
" message
" :
" Ca
nn
o
t
move
a
f
ile
i
nt
o
a
shared
drive
as
a
wri
ter
whe
n
t
he
ow
ner
o
f
t
he
f
ile
is
n
o
t
a
member
o
f
t
ha
t
shared
drive.
"
}
}
To fix this error:
-
Add the member to the shared drive with
role=owner. For more information, see Share files, folders, and drives . -
Add the file to the shared drive. For more information, see Create and populate folders .
fileWriterTeamDriveMoveInDisabled
This error occurs when a domain administrator hasn't allowed users with role=writer
to move items into a shared drive. The user attempting to move the
items has fewer permissions than allowed on the destination shared drive. The
following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" f
ileWri
ter
TeamDriveMoveI
n
Disabled
" ,
" message
" :
" The
domai
n
admi
n
is
trat
or
has
n
o
t
allowed
wri
ters
t
o
move
i
te
ms
i
nt
o
a
shared
drive.
"
}
],
" code
" :
403
,
" message
" :
" The
domai
n
admi
n
is
trat
or
has
n
o
t
allowed
wri
ters
t
o
move
i
te
ms
i
nt
o
a
shared
drive.
"
}
}
To fix this error, use the same administrator user account on both the source and destination shared drives.
insufficientFilePermissions
This error occurs when the user doesn't have write access to a file, and your app is attempting to modify the file. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" i
nsuff
icie
nt
FilePermissio
ns
" ,
" message
" :
" The
user
does
n
o
t
have
su
ff
icie
nt
permissio
ns
f
or
f
ile
{
f
ileId
}
.
"
}
],
" code
" :
403
,
" message
" :
" The
user
does
n
o
t
have
su
ff
icie
nt
permissio
ns
f
or
f
ile
{
f
ileId
}
.
"
}
}
To fix this error, instruct the user to contact the file's owner and request
edit access. You can also check user access levels in the metadata retrieved by
the files.get
method and display a
read-only UI when permissions are missing.
myDriveHierarchyDepthLimitExceeded
A myDriveHierarchyDepthLimitExceeded
error occurs when the limit for the
number of nested folder levels has been exceeded. A user's My
Drive can't contain more than 100 levels of nested folders. For
more information, see Folder-depth
limit
.
{
" error
":
{
" errors
":
[
{
" domain
":
" global
",
" reason
":
" myDriveHierarchyDepthLimitExceeded
",
" message
":
" Your
My
Drive
can't
contain
more
than
100
levels
of
folders
.
For
details
,
see
https
: //
developers
. google
. com
/
drive
/
api
/
guides
/
handle
-
errors
# nested
-
folder
-
levels
."
}
],
" code
":
403
,
" message
":
" Your
My
Drive
can't
contain
more
than
100
levels
of
folders
.
For
details
,
see
https
: //
developers
. google
. com
/
drive
/
api
/
guides
/
handle
-
errors
# nested
-
folder
-
levels
."
}
}
To fix this error:
- Inform the user that Drive prevents placing folders more than 100 levels deep.
- If the user must create another nested folder, instruct them to reorganize the intended parent folder to be fewer than 100 levels deep or use a different parent folder that already meets the requirement.
numChildrenInNonRootLimitExceeded
This error occurs when the limit for a folder's number of children (folders, files, and shortcuts) has been exceeded. There's a 500,000 item limit for folders, files, and shortcuts directly in a folder. Items nested in subfolders don't count against this 500,000 item limit. For more information on Drive folder limits, refer to Folder limits in Google Drive .
The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" nu
mChildre
n
I
n
No
n
Roo
t
Limi
t
Exceeded
" ,
" message
" :
" The
limi
t
f
or
t
his
f
older's
nu
mber
o
f
childre
n
(
f
iles
a
n
d
f
olders)
has
bee
n
exceeded.
"
}
],
" code
" :
403
,
" message
" :
" The
limi
t
f
or
t
his
f
older's
nu
mber
o
f
childre
n
(
f
iles
a
n
d
f
olders)
has
bee
n
exceeded.
"
}
}
To fix this error, try any of the following:
- Inform the user that Drive prevents folders with more than 500,000 items.
- If the user must add more items to the full folder, instruct them to reorganize the folder to contain fewer than 500,000 items or use a similar folder that already contains fewer items.
rateLimitExceeded
This error occurs when the project's rate limit has been reached. This limit varies depending on the type of request. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" usageLimi
ts
" ,
" message
" :
" Ra
te
Limi
t
Exceeded
" ,
" reaso
n
" :
" ra
te
Limi
t
Exceeded
" ,
}
],
" code
" :
403
,
" message
" :
" Ra
te
Limi
t
Exceeded
"
}
}
To fix this error, try any of the following:
- Raise the per-user quota in the Google Cloud project. For more information, request a quota increase .
- Batch requests to bundle multiple API calls into one HTTP request.
- Use exponential backoff to retry the request.
sharingRateLimitExceeded
This error occurs when the user reaches a sharing limit and is often linked with an email limit. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" message
" :
" Ra
te
limi
t
exceeded.
User
message
:
\"These
i
te
m(s)
could
n
o
t
be
shared
because
a
ra
te
limi
t
was
exceeded
:
f
ile
na
me
" ,
" reaso
n
" :
" shari
n
gRa
te
Limi
t
Exceeded
" ,
}
],
" code
" :
403
,
" message
" :
" Ra
te
Limi
t
Exceeded
"
}
}
To fix this error:
- Don't send emails when sharing large amounts of files.
- If one user is making numerous requests on behalf of many users of a
Google Workspace account, consider a service account with domain-wide
delegation
using the
quotaUserparameter .
storageQuotaExceeded
This error occurs when the user reaches their storage limit. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" message
" :
" The
user's
Drive
s
t
orage
quo
ta
has
bee
n
exceeded.
" ,
" reaso
n
" :
" s
t
orageQuo
ta
Exceeded
" ,
}
],
" code
" :
403
,
" message
" :
" The
user's
Drive
s
t
orage
quo
ta
has
bee
n
exceeded.
"
}
}
To fix this error:
-
Review your Drive account storage limits. For more information, refer to Google Workspace storage and upload limits .
teamDriveFileLimitExceeded
This error occurs when a user attempts to exceed the strict item limit on a shared drive. Each folder in a user's shared drive has a limit of 500,000 items, including files, folders, and shortcuts. This limit is based on item count, not storage use. For more information, see Shared drive limits in Google Drive .
The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" tea
mDriveFileLimi
t
Exceeded
" ,
" message
" :
" The
f
ile
limi
t
f
or
t
his
shared
drive
has
bee
n
exceeded.
"
}
],
" code
" :
403
,
" message
" :
" The
f
ile
limi
t
f
or
t
his
shared
drive
has
bee
n
exceeded.
"
}
}
To fix this error, reduce the number of items in the shared drive. Shared drives with too many files might be difficult to organize and search.
teamDriveHierarchyTooDeep
A teamDriveHierarchyTooDeep
error occurs when the limit for the number of
shared drive nested folder levels has been exceeded. A user's shared drive can't
contain more than 100 levels of nested folders. For more information, see Folder-depth limit
.
{
"error": {
"errors": [
{
"domain": "global",
"reason": "teamDriveHierarchyTooDeep",
"message": "The shared drive hierarchy depth will exceed the limit."
}
],
"code": 403,
"message": "The shared drive hierarchy depth will exceed the limit."
}
}
To fix this error:
- Inform the user that shared drives prevents placing folders more than 100 levels deep.
- If the user must create another nested folder, instruct them to reorganize the intended parent folder to be fewer than 100 levels deep or use a different parent folder that already meets the requirement.
teamDriveMembershipRequired
This error occurs when a user attempts to access a shared drive in which they're not a member. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" tea
mDriveMembershipRequired
" ,
" message
" :
" The
a
tte
mp
te
d
ac
t
io
n
requires
shared
drive
membership.
"
}
],
" code
" :
403
,
" message
" :
" The
a
tte
mp
te
d
ac
t
io
n
requires
shared
drive
membership.
"
}
}
To fix this error, try any of the following:
-
Ask the manager of the shared drive to add you with the appropriate permissions for the action you must perform.
-
Review Drive's Roles and permissions to learn who can access and manage shared drives. Additional information about access levels can also be found at Create a shared drive .
teamDrivesFolderMoveInNotSupported
This error occurs when a user attempts to move a folder from My Drive into a shared drive. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" tea
mDrivesFolderMoveI
n
No
t
Suppor
te
d
" ,
" message
" :
" Movi
n
g
f
olders
i
nt
o
shared
drives
is
n
o
t
suppor
te
d.
"
}
],
" code
" :
403
,
" message
" :
" Movi
n
g
f
olders
i
nt
o
shared
drives
is
n
o
t
suppor
te
d.
"
}
}
To fix this error, try any of the following:
-
Move the individual items from the folder into a shared drive using the Drive API. Set the
supportsAllDrives=trueparameter to denote the support of both My Drive and shared drives. -
If you must move the folder into a shared drive, use the Drive UI. For more information, see Move folders into shared drives as an admin .
teamDrivesParentLimit
This error occurs when a user attempts to add more than one parent to an item in a shared drive. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" tea
mDrivesPare
nt
Limi
t
" ,
" message
" :
" A
shared
drive
i
te
m
mus
t
have
exac
tl
y
o
ne
pare
nt
.
"
}
],
" code
" :
403
,
" message
" :
" A
shared
drive
i
te
m
mus
t
have
exac
tl
y
o
ne
pare
nt
.
"
}
}
To fix this error, use Drive shortcuts to add multiple links to a file. Although a shortcut can only have one parent, a shortcut file can be copied to the additional locations. For more information, see Create a shortcut to a Drive file .
UrlLeaseLimitExceeded
This error occurs when trying to save Google Play game data through your application. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" usageLimi
ts
" ,
" reaso
n
" :
" UrlLeaseLimi
t
Exceeded
" ,
" message
" :
" Too
ma
n
y
pe
n
di
n
g
uploads
f
or
t
his
s
na
psho
t
.
Please
f
i
n
ish
or
ca
n
cel
some
be
f
ore
crea
t
i
n
g
more.
"
}
],
" code
" :
403
,
" message
" :
" Too
ma
n
y
pe
n
di
n
g
uploads
f
or
t
his
s
na
psho
t
.
Please
f
i
n
ish
or
ca
n
cel
some
be
f
ore
crea
t
i
n
g
more.
"
}
}
To fix this error, complete or cancel any uploads for a snapshot before creating more.
userRateLimitExceeded
This error occurs when the per-user limit has been reached. This might be a limit from the Google Cloud console or a limit from the Drive backend. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" usageLimi
ts
" ,
" reaso
n
" :
" userRa
te
Limi
t
Exceeded
" ,
" message
" :
" User
Ra
te
Limi
t
Exceeded
"
}
],
" code
" :
403
,
" message
" :
" User
Ra
te
Limi
t
Exceeded
"
}
}
To fix this error, try any of the following:
-
Raise the per-user quota in the Google Cloud project. For more information, request a quota increase .
-
If one user is making numerous requests on behalf of many users of a Google Workspace account, consider a service account with domain-wide delegation using the
quotaUserparameter . -
Use exponential backoff to retry the request.
For information about Drive API limits, refer to Usage limits .
404 errors
These errors mean that the requested resource isn't accessible or doesn't exist.
notFound
This error occurs when the user doesn't have read access to a file, or the file doesn't exist. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" global
" ,
" reaso
n
" :
" n
o
t
Fou
n
d
" ,
" message
" :
" File
n
o
t
f
ou
n
d
{
f
ileId
}
"
}
],
" code
" :
404
,
" message
" :
" File
n
o
t
f
ou
n
d
:
{
f
ileId
}
"
}
}
To fix this error:
- If the file is located in a shared drive, and you're using the
files.getmethod, make sure thesupportsAllDrivesquery parameter is set totrue. - Inform the user that they don't have read access to the file or the file doesn't exist.
- Instruct the user to contact the file's owner and request permission to the file.
429 errors
These errors mean that too many requests were sent to the API too quickly.
rateLimitExceeded
This error occurs when the user has sent too many requests in a given amount of time. The following JSON sample is a representation of this error:
{
" error
" :
{
" errors
" :
[
{
" domai
n
" :
" usageLimi
ts
" ,
" reaso
n
" :
" ra
te
Limi
t
Exceeded
" ,
" message
" :
" Ra
te
Limi
t
Exceeded
"
}
],
" code
" :
429
,
" message
" :
" Ra
te
Limi
t
Exceeded"s
}
}
To fix this error, use exponential backoff to retry the request.
500, 502, 503, 504 errors
These errors occur when an unexpected server error arises while processing the request. Various issues can cause these errors, including a request's timing overlapping with another request or a request for an unsupported action, such as attempting to update permissions for a single page in Google Sites instead of the entire site.
The following is a list of 5xx errors:
- 500 Backend error
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
To fix this error, use exponential backoff to retry the request.
