Why Has the Google Drive Trigger Stopped Monitoring New Files in the Workflow?

Help
61

Oh

62

I can’t go back further than 12:06:40

63

hold on, let me recreate the entire thing and look asap

64

I was asking because we dedupe events using the fileID and the headers["x-goog-message-number"] field:
${fileId}-${headers["x-goog-message-number"]}

65

So if the headers["x-goog-message-number"] is different for the two events then Google is sending the same exact event twice

66

Couldn’t recreate this time.

  1. Deleted a file.
  2. Waited 1 second.
  3. Uploaded the file.
    1 event generated:
67

FYI your endpoint is exposed in the screenshot

68

Sigh. Never easy

69

So as it stands with this last run…only 1 event was generated

70

after deleting, then re-uploading

71

I’ll try another.

72

Ok. I’m looking at the logs

73

That time I waited 4-5 seconds…

74

just the 1 event generated

75

so i’m not sure about that first set of dupes:

76

image.png
image.png552×608 29 KB

77

But otherwise appears…fixed?

78

Hmm can’t be that easy

79

:shrug:

80

Ok so I see that there may be more than one page of changes with each request. But we use the same value for headers["x-goog-message-number"] to dedupe. Maybe it’s better to use the timestamp of the change, but then again there were two events with the exact same timestamp