I have a recipe that is monitoring a specific column in a google sheet for changes. In my case, it's a column called Status. Once the user updates the Status in a row, if the new Status meets the trigger criteria, it should trigger the recipe to run.
My recipe works well when I first run it. But I started noticing during testing that if I update the Status back to a value that had previously triggered the recipe, the trigger will not pick up that update. For instance, a Status of "Add to Calendar" triggers the recipe to run, and the last step of my recipe will change the status to "Scheduled." If I then happen to make an edit to other fields in that row and then put the Status back to "Add to Calendar," the trigger will not pick up that update.
Does the "New/updated sheet row" trigger inherently only pick up unique values in the column being monitored? If so, how might I get around this if my intention is to trigger my recipe any time that Status field is changed to the value I set up as my trigger criteria?
'New/updated sheet row' triggers monitor a predetermined column for any changes, provided the recipe is running. You can read more about it here: http://resources.workato.com/googlesheets-connector/#/list/3?_k=6500oe
I was testing with my recipes running, and got the results I've described. I also had read through the documentation and it's not explicit about what constitutes a "change" to the monitored column.
Hi Brad, here is a video explaining the behavior of the Google Sheets trigger.
As a Partner, you are entitled to ticketed support. Would you like to submit a ticket so that we can diagnose the issue you are facing?
Helpful video Justin, you gave me the answer I was looking for - yes, the trigger should pick up values that have previously been processed through the recipe. I'll go ahead and submit a ticket.
As an additional note, there is a limitation to the Google sheets new/updated row trigger - updates to sheet rows can only be picked up for a maximum of 1000 rows. You may need to find another way to achieve your use case if you have a very large number of rows to monitor.
Send us a ticket, we will try our best to assist you with your problem