News
MAINTENANCE AND SERVICE UPDATES A patch (v3.1.2.1) will be applied to BinderCloud Production v3.1.2.0, and will be available from Monday 28th March 2016. Update v3.0: Wed 11:53 Sunless Skies: Sovereign Edition Patch Notes: Wed 11:28 BARRICADEZ: Some Finishing Touches (4.01) Wed 11:28 Human Factory: Hotfix: Wed 11:27 The Hand of Merlin: Dev blog 69 - Early access week 1: Wed 11:25 Where Wind Becomes Quiet: 0.9.6 - version: Wed 11:25 Grim Nights: Patch 1.3.3.2 - Potion fix! Wed 11:23 ShemHaMephorash. Join the Patch V3 Movement! Get in touch today. We strive for complete customer satisfaction, and will be in contact with you as quickly as we can. Name. Email. Message. FREE SHIPPING & RETURN. Free shipping on all North America orders over. 1,272 likes 34 talking about this. Patch V3 is a natural and innovative way to optimize your intake of vitamins and supplements without ingesting harmful fillers. Patch V3 patches are.
***NEW***Production Maintenance and Service Updates19/06/2017
* Service Notice *03/05/2017
***NEW***Production Maintenance and Service Updates21/04/2017
* Service Notice *18/04/2017
***NEW***Production Maintenance and Service Updates08/04/2017
Maintenance and service updates10/02/2017
Maintenance and service updates08/02/2017
***NEW***Production Maintenance and Service Updates03/01/2017
***NEW***Production Maintenance and Service Updates29/12/2016
***NEW***Production Maintenance and Service Updates29/12/2016
***NEW***Production Maintenance and Service Updates23/11/2016
***NEW***Production Maintenance and Service Updates23/09/2016
Maintenance and service updates31/08/2016
Production Maintenance and Service Updates12/08/2016
Production Maintenance Service Updates14/06/2016
Production Maintenance and Service Update12/06/2016
Production Maintenance Service Updates13/05/2016
Production Maintenance Service Updates24/03/2016
Log on issues Resolved09/03/2016
Production Maintenance Service Updates04/03/2016
UAT Maintenance and Service Updates18/02/2016
Production Maintenance Service Updates03/02/2016
**NEW**UAT Maintenance Service Updates20/01/2016
Production Maintenance Service Updates15/01/2016
Scheduled Maintenance for Microsoft Azure13/01/2016
UAT Maintenance Service Updates31/12/2015
UAT Maintenance Service Updates22/05/2015
UAT Maintenance Service Updates24/04/2015
Production Maintenance Service Updates12/12/2014
UAT Maintenance Service Updates28/11/2014
UAT Maintenance Service Updates31/10/2014
Production and Maintenance Service Updates17/10/2014
Production and Maintenance Service Updates19/09/2014
UAT Maintenance and Service Updates05/09/2014
Production Maintenance and Service Updates26/08/2014
UAT Maintenance and Service Updates26/08/2014
Production Maintenance and Service Updates02/07/2014
UAT Maintenance and Service Updates16/06/2014
Production Maintenance and Service Updates02/06/2014
UAT Maintenance and Service Updates 16/05/201419/05/2014
Production Maintenance and Service Updates06/05/2014
UAT Maintenance and Service Updates19/04/2014
Production Maintenance and Service Updates03/04/2014
UAT Maintenance and Service Updates21/03/2014
UAT Maintenance and Service Update22/02/2014
UAT Maintenance and Service Updates10/02/2014
Production Maintenance and Service Update10/02/2014
UAT Maintenance and Service Update17/01/2014
Production Maintenance and Service Updates10/01/2014
UAT, System Test maintenance and serviice updates13/12/2013
Production Maintenance and Service Updates29/11/2013
System Test version release27/08/2013
Production version release27/08/2013
Appid Patch V3 Download
UAT Maintenance and Service Updates15/07/2013
Maintenance and service updates27/06/2013
Appid Patch V3
The Drive API returns two levels of error information:
- HTTP error codes and messages in the header.
- A JSON object in the response body with additional details that can help youdetermine how to handle the error.
Drive apps should catch and handle all errors that might be encountered whenusing the REST API. This guide provides instructions on how to resolve specificAPI errors.
Resolve a 400 error: Bad request
This error can result from any one of the following issues in yourcode:
- 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.
Following is a sample JSON representation of this error:
To fix this error, check the message field and adjust your code accordingly.
Resolve a 400 error: Invalid sharing request
This error can occur for several reasons. To determine the limitthat has been exceeded, evaluate the reason field of the returned JSON.This error most commonly occurs because:
- sharing succeeded, but the notification email was not correctly delivered.
- the ACL change is not allowed for this user.
The message field indicates the actual error.
Sharing succeeded, but the notification email was not correctly delivered.
Following is the JSON representation of this error:
To fix this error, inform the user (sharer) that they were unable to sharebecause the notification email couldn't be sent to the sharee. The user shouldensure they have the correct email address and that the sharee can receiveemail.
The ACL change is not allowed for this user.
Following is the JSON representation of this error:
To fix this error, check the sharing settings of theGoogle Workspace domain to whichthe file belongs. The sharing settings might be prohibiting sharing outside ofthe domain or sharing a shared drive might not be permitted.
Resolve a 401 error: Invalid credentials
A 401 error indicates that the access token you're using is either expiredor invalid. This error can also be caused by missing authorization for therequested scopes. Following is the JSON representation of this error:
To fix this error, refresh the access token using the long-lived refreshtoken. If this fails, direct the user through the OAuth flow, as describedin Authorizing Your App with Google Drive.
Resolve a 403 error: Usage limit exceeded
An error 403 occurs when a usage limit has been exceeded or the user doesn'thave the correct privileges. To determine the specific type of error, evaluatethe reason field of the returned JSON. This error occurs for the followingsituations:
- The daily limit was exceeded.
- The user rate limit was exceeded.
- The project rate limit was exceeded.
- The sharing rate limit was exceeded.
- The user hasn't granted your app rights to a file.
- The user doesn't have sufficient permissions for a file.
- Your app can't be used within the authenticated user's domain.
Resolve a 403 error: Daily limit exceeded
A dailyLimitExceeded error indicates that the courtesy API limit for yourproject has been reached. Following is the JSON representation of this error:
To fix this error:
- Visit the Google API Console
- Select your project.
- Click the Quotas tab
- Request additional quota. For more information, seeRequest additional quota.
Resolve a 403 error: Number of items in folder
A numChildrenInNonRootLimitExceeded error occurs when the limit for afolder's number of children (folders, files, and shortcuts) has been exceeded.There is a 500,000 item limit for folders, files, and shortcuts directly in afolder. Items nested in subfolders do not count against this 500,000 itemlimit. For more information on folder limits, refer toFolder limits in Google Drive.
Resolve a 403 error: User rate limit exceeded
A userRateLimitExceeded error indicates that the per-user limit has beenreached. This limit might be the limit from the API console or a limitfrom the Drive backend. Following is the JSON representation of this error:
To fix this error:
- Raise the per-user quota in the Developer Console project. For moreinformation, see Request additional quota.
- If one user is making a lot of requests on behalf of many users of aGoogle Workspace domain, consider aService Account with authoritydelegation (setting the quotaUser parameter).
- Use exponential backoff to retry the request.
Resolve a 403 error: Rate limit exceeded
A rateLimitExceeded error indicates that the user has reached Google DriveAPI's maximum request rate. This limit varies depending on the type of requests.Following is the JSON representation of this error:
To fix this error:
- Batch the requests.
- Use exponential backoff to retry the request.
Resolve a 403 error: Sharing rate limit exceeded
A sharingRateLimitExceeded error occurs when the user has reached a sharinglimit. This error is often linked with an email limit. Following is the JSONrepresentation of this error:
To fix this error:
- Do not send emails when sharing lot of files.
- If one user is making a lot of requests on behalf of many users of aGoogle Workspace domain, consider aService Account with authoritydelegation to impersonate the owner of each document to share(setting the quotaUser parameter).
Resolve a 403 error: The user has not granted the app {appId} {verb} access to the file {fileId}
An appNotAuthorizedToFile error occurs when your app is not on theACL for the file. This error prevents the user from opening the file with yourapp. Following is the JSON representation of this error:
To fix this error, perform one of the following operations:
Appid Patch V3 Download
- Open the Google Drive pickerand prompt the user to open the file.
- Instruct the user to use your app to open the file using the Open withcontext menu in the Drive UI.
You can also check the isAppAuthorized field on a file to see if the filewas created by or opened with your app.
Resolve a 403 error: The user does not have sufficient permissions for file {fileId}
A insufficientFilePermissions error occurs when the user does not have writeaccess to a file, and your app is attempting to modify that file. Following isthe JSON representation of this error:
To fix this error, instruct the user to contact the file's owner and requestedit access. You can also check user access levels in the metadata retrieved byfiles.get and display a read-only UI whenpermissions are missing.
Resolve a 403 error: App with id {appId} cannot be used within the authenticated user's domain
A domainPolicy error occurs when the policy for the user's domain doesn'tallow access to Google Drive by your app. Following is the JSON representationof this error:
To fix this error:
- Inform the user that the domain doesn't allow your app to access files inDrive.
- Instruct the user to contact the domain Admin to request access for your app.
Resolve a 404 error: File not found: {fileId}
The notFound error occurs when the user does not have read access to a file,or the file does not exist.
To fix this error:
- Inform the user they don't have read access to the file or that the filedoesn't exist.
- Instruct the user to ask the owner for permission to the file.
Resolve a 429 error: Too many requests
A rateLimitExceeded error occurs when the user has sent too many requests in
a given amount of time.
To fix this error, use exponential backoff to retrythe request.
Resolve a 500 error: Backend error
A backendError occurs when an unexpected error arises while processing therequest. This can be caused by a variety of issues, including a request's timingoverlapping with another request or a request for an unsupported action, such asattempting to update permissions for a single page in a Google Site instead of thesite itself.
To fix this error, use exponential backoff to retrythe request. Following is a list of 500 errors:
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
Retry failed requests to resolve errors
You can periodically retry a failed request over an increasing amount of time tohandle errors related to rate limits, network volume, or response time. Forexample, you might retry a failed request after one second, then after twoseconds, and then after four seconds. This method is calledexponential backoff and it is used to improve bandwidth usage and maximizethroughput of requests in concurrent environments. When using exponentialbackoff, consider the following:
- Start retry periods at least one second after the error.
- If the attempted request introduces a change, such as a create request, add acheck to make sure nothing is duplicated. Some errors, such as invalidauthorization credentials or 'file not found' errors, aren’t resolved byretrying the request.
Request additional quota
If you believe you need additional quota:
- Visit the Google API Console
- Select your project.
- Click the Quotas tab.
- Request additional quota.
Only request additional quota if your application exceeds the Drive API courtesylimit or the per-user limit. If exceeding the per-user limit, try to optimizeyour application code to make fewer requests.