You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Our trigger uses the last processed row number to know when to emit new rows. This causes issues if a row is deleted and then another one is created, since it will be exactly the same row number as the last one processed (and can be lower).
I'll make some tests to see if we can address this issue.
Additional context
User also said that if the sheet is updated via a workflow or external service (e.g. Google Forms), then Google Sheets doesn't send the webhook immediately and requires the spreadsheet to be open in a computer.
The text was updated successfully, but these errors were encountered:
Describe the bug
Our trigger uses the last processed row number to know when to emit new rows. This causes issues if a row is deleted and then another one is created, since it will be exactly the same row number as the last one processed (and can be lower).
I'll make some tests to see if we can address this issue.
Additional context
User also said that if the sheet is updated via a workflow or external service (e.g. Google Forms), then Google Sheets doesn't send the webhook immediately and requires the spreadsheet to be open in a computer.
The text was updated successfully, but these errors were encountered: