Twice since I switched to the new Salesforce integration, one of my Zaps, whose trigger event is ‘Updated Field on Record’, has done a mass processing of Projects that were marked as Completed a long time ago. I awoke to an email from Zapier saying
> We're reaching out to let you know that we're holding 101 Tasks for your Zap: "SF-Complete status triggers celebration to Slack finish line 1.0.1".
Of course, nobody went in last night and marked 101 Projects as Completed. So, what’s causing this? Given that this is the 2nd time this has happened, I’m concerned that the new Salesforce integration which triggers on an updated record field isn't working properly.
Or, could it be, dare I say it, operator error? Nah, couldn’t be that. :)
Curious if this is working fine for everyone else? It’s a shame since being able to trigger on an updated field on record is something I had wanted to do for a long time. Now, I’m considering approaching my zaps w/o this ability due to the grief it is causing me.
Best answer by jesse
I think what we're seeing here is a problem that extends across multiple apps. I don't think it's a bug per se, but something that can happen when you have a large number of records in many Apps.
When we check for new records, we tell Salesforce to sort them in descending order by modified date. This allows us to see the most recently updated records and if they have the value you're checking for, then Trigger on them. The problem is that there are so many records, that when we initially turn on the Zap to see what already exists, we're only seeing about half your records (I think, based on looking at the query results and their API docs).
What that means is that if older records that were never seen previously get updated - maybe they're archived or moved in some way - I'm not sure, these records bubble to the top and the Zap sees them for the first time. Because they all have the Status "Completed", they all Trigger, too.
Is it possible to create a new Status for your Projects? Here's what I'm thinking we can try as a workaround:
- If you can create a new Status, make one called "Just Completed" or "Completed Zap" or something like that.
- Set the Zap to Trigger from that new Status instead
- Add a Step to the Zap to change the Status from the new one to the familiar "Completed" status.
- By doing that, we can still Trigger the Zap, but after the Zap has Triggered, the record will be altered in a such a way that it won't Trigger the Zap again, and the existing older records won't Trigger the Zap if they're updated, either.
Let us know if Tim’s workaround helped you here!