Skip to main content

I have a number of automations that have been working for years that suddenly stopped finding records as of the first time they ran in July. They were supposed to be looking for records in a related view, but were listing Condition Filters that had nothing to do with that view.

I tried changing them to use Conditions instead of a View, and there were condition filters defined, apparently from copying another automation and then modifying it. They have been this was as far as I know from the beginning, but worked based on the View filters until July.

I have cleared out the unused condition filters and am waiting for the first run in August to verify it is fixed. Just wanted to figure out why they used to work and quit without changes on my part.

Hey ​@Tom_Embaugh,

1. If you suspect this is a bug, then you might want to reach out to support@airtable.com
2. Either way, feel free to grab a slot using this link and we can quickly go through it together.  If this is not a bug, then we should be able to get is fixed in a few minutes!

Mike, Consultant @ Automatic Nation

Hm, that’s a weird one.  When you look at the Run History, the previous runs are all good and use the View for the Find Record step?  And when you look at the Revision History no changes have been made for months?

​@Mike_AutomaticN not sure if it is a bug. But I did make the change already to remove the condition filters from the automation. Thanks for the offer. If it all starts working after the change I will notify support.

​@TheTimeSavingCo the last change in the automation was 9/23. So the behavior change is not from that. The run history details below show the view AND conditions for at least several months into the past, but successfully found the records based on the view and sent out the emails up until the first run in July. the 4 runs in July were “successful” and did not throw an error, but did not find any records or send any emails. The end user notified me he was no longer getting the emails or I would not even be checking it.

 

Wow, that screenshot’s crazy!  I just spent some time trying to replicate the screenshot and couldn’t either and feel like you stumbled on a bug of some sort

So the ‘Find record’ step had both ‘View’ and ‘Condition’ there, and then you manually deleted the ‘Conditions’?  What was the ‘Find records based on’ input field set to?  Sorry that I can’t help, I’m just fascinated with this but totally get if you’re too busy to respond!

The Find Records was based on the view, and as it turns out this weirdness is not what stopped the  automation. It was some dates that the views were dependent on that were off by a month. Once I fixed those things started working again.

So not a bug since the automation worked fine with the issue, but I cleaned them up anyway.

Terms & ConditionsAccessibility statement