Handle 404 errors when making changes to Google Drive

Question

I am working on an application that monitors user accounts for changes using a watchdog . With every incoming change, our application then proceeds to restore using get endpoint so that it can be processed correctly.

However, there are certain cases when a request for a change returns a 404 error. We were able to reliably reproduce this problem with image files, in particular png and jpeg, by dragging the file from the computer to the disk user interface to load it. Oddly enough, this problem does not occur for most file types (as far as we have seen).

We tried using exponential retry, but there seems to be no change. This is an example of the answer I received through the tools in the API documentation to get a specific change that had this problem.

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notFound",
    "message": "Change not found: 18061",
    "locationType": "other",
    "location": "change"
   }
  ],
  "code": 404,
  "message": "Change not found: 18061"
 }
}

One possible workaround for the solution that we are considering when using would be to execute a query in all user files using the modifiedDate parameter to search for files in the last 10 seconds or so, but processing the changes directly is a much better way to work.

Update

We played with this a bit more and found some other cases where changes reliably return 404 errors:

• When a file of any type is moved to the trash (if you open it when it is in the trash, a real change occurs)
• When a file of any type is deleted from the trash

2

, , 1 "changeId", , API, , . ...

3

, , "changeId", , 2 .

Answer 1

, , , , , . , .

, , , , . Changes.list() startChangeId , .