Hi all,
I’m having difficulty getting a google sheets “Watch new rows” to run reliably. I’ve done some searching here and on the web as a whole, and haven’t found anything that seems to match my problem.
Basics
- We have a google Form adding records to a Sheet. The form contains a script with a webhook.
- A second Sheet collects that info and adds some other columns.
- We then use the 2nd Sheet’s data to send off to Clickup.
Setup
Scenario 1: Form Listener Trigger.
A “Custom webhook” module (listens for the google Form) to a “Run a Scenario” module (triggers Scenario 2)
Scenario 2: Create task(s)
Starts with a “Watch New Rows” linked to the 2nd Google Sheet. Everything downstream works great.
Issue
- Scenario 1 always runs perfectly.
- Scenario 2 works perfectly most of the time.
- After not running for a while (overnight/over a weekend), Scenario 2 sometimes has a Check Run.
- After this Check Run, the sheet will be 1 row behind, so that with the next submission the Sheet will find the data missed by the previous run.
example: Submission 1 has a check run. Submission 2 then triggers with the data from submission 1. Submission 3 will find data from Submission 2, etc.
- I fix this manually by manually setting the starting row, run it once, and it works reliably for a day or two.
Notes
The closest thing to a solution I can find is from this thread: "watch Changes" on google sheet - not triggering on new row added
which suggests a timestamp column. I can do this if necessary, but I’m hoping there is just some setting I’ve overlooked to stop the Watch New Rows module from losing its place.
I have the Watch New Row limit set to 1, if that’s relevant.
We’ve only been running this for a week, and the issue has happened 3 times, so the “only happens after not running for a while” may just be coincidence, but it’s only happened with the first record submitted that day.
Thanks in advance for any help.
1 Like
Hi @Tobermory_Press
At how much interval of time you have scheduled the trigger?? And how many records you expect to recieve between that interval of time??
Although, you should increase the limit and check runs doesn’t affect the data. It always process the new data if it is there and didn’t process yet.
Regards,
Msquare Automation - Platinum Partner of Make
@Msquare_Automation
The trigger is not timed. There is a webhook set to “immediately” on scenario 1, which then runs scenario 2. Scenario 2’s “Watch New Rows” is set to “on demand”.
Why would increasing the limit matter, since there will only ever be 1 new record per run?
1 Like
Hi @Tobermory_Press
You first scenario is only watching for google form submissions and then triggering the other module to run.
When the data is always going into google sheet, why do you need to watch for google form as well? You can choose any one trigger among form and sheet.
In your current case, you need some seconds of delay in your first scenario as it takes time to reflect in the sheet sometimes.
Otherwise, the simple method is you can just discard any one of the workflow and do the action in same one.
Regards,
Msquare Automation - Platinum Partner of Make
@Msquare_Automation
I settled on watching the Form because I need the automation to run as soon as data is received. As I understand it, the Google Sheet Watch New Rows module could only be set to run at intervals or manually.
If there is a way to have Watch New Rows trigger as soon as a new row is added, I would gladly drop the Form webhook. Or are you suggesting to move the webhook to the start of Scenario 2? I don’t see how that would be any different than my current setup, other than using 1 fewer operation per run, and it would no longer have any delay.
For the time being, I’ve upped the delay on Scenario 1’s Run a Scenario module to 30s (it was at 10s).
I appreciate your help with this.
The 30s delay didn’t help.
Is there any way to get “Watch new rows” to run immediately upon a new row being added? That seems to be what was suggested with “…discard any one of the workflow…”, but I don’t see how it’s possible.