Google Sheets - New Row Added source suddenly stopped emitting new rows

Help
61

Dylan Sather (Pipedream) : hopefully my last ping for the day. Trever and I were chatting over DM and he asked about pagination for this API call. I looked into the docs and it looks like the REST API for changes.list defaults to returning the last 100 changes. It’s not clear whether the Node SDK will handle pagination on our behalf from the docs, but they do also take a maxResults param (and return a nextLink), so I wonder if that could be it. If we accrue more than 100 changes for the user’s drive since the last time the spreadsheet was edited, I can see how we could miss the change and get into this state

62

Dylan Sather (Pipedream) : (drive.changes.list docs here)

63

Trever Faden : any chance we’ll be able to get this patched today? I have some business processes that are backed up because of the bug :disappointed:

64

Dylan Sather (Pipedream) : yes, I believe I can get it working for you. Do you mind if I edit the source’s code?

65

Trever Faden : go for it

66

Dylan Sather (Pipedream) : Would you mind adding one more row of test data to your spreadsheet?

67

Trever Faden : hey now!

68

Trever Faden : that worked!

69

Dylan Sather (Pipedream) : great, I would recommend simply copying and pasting the two rows that failed to emit now

70

Dylan Sather (Pipedream) : at the bottom of the spreadsheet

71

Dylan Sather (Pipedream) : and those should also emit successfully now

72

Dylan Sather (Pipedream) : then we’ll address the pagination issue ASAP and get you a new version of the source you can use

73

Trever Faden : :+1: thank you!

74

Jay Vercellone : Hey there! Sorry for the delay

75

Jay Vercellone : Did you implement the change in your workflow? Or in the repo?

76

Dylan Sather (Pipedream) : Jay I simply reset the most recent pageToken in Trever’s source and ran it again, which let us grab more recent rows. I haven’t made any changes to the way we list drive changes. Do you think that hypothesis makes sense?

77

Dylan Sather (Pipedream) : i.e. the stuff about pagination with the call to drive.changes.list ?

78

Jay Vercellone : So basically the pageToken that we cached was too far behind?

79

Dylan Sather (Pipedream) : that’s right, and I believe we only list the first 100 changes since that page token, and that didn’t include the changes to this spreadsheet

80

Dylan Sather (Pipedream) : too many changes to other files had processed in the meantime