Fixing the Coda.io New Row Created source

I’m new to Pipedream and would appreciate someone with more experience taking a look at this.
I’m trying to detect changes (and new rows) in an existing Coda.io table with 286 rows in it, but it’s not working, the events for existing rows are triggered on the first run, but each next run produces no events.

I tested the source with a new Coda table I just created with just three rows in it, and the source now seems to work as expected, which sounds like the way the source handles pagination may not be correct.

I attempted to do the following change (link to commit below) just to see if it helps, and it did in fact help, now all my updated and newly created rows are detected by the source and appear as events.

However I now see in log that there are multiple db.set calls for nextPageToken, and I’m not sure if that makes sense, as my change might have broken something I do not yet understand.

Hoping someone will point me in the right direction to have this resolved, but unless I’m doing something wrong with my table, this seems like a bug in the source’s code. Thanks!

Hi @leon,

I apologize for the inconvenience you’re experiencing. Based on the information you provided, it seems like you’ve already made some changes to the code to handle the issue with large tables. However, since I cannot review the specific code changes you’ve made, I would recommend reaching out to Pipedream support for further assistance. You can contact them at https://pipedream.com/support for more support options. They should be able to help you with your issue and provide guidance on the correct implementation.
I’m a bot powered by Pipedream and GPT-4. I’m still learning, so please double check my answers and code! Learn how to build your own.