Skip to main content

My filter doesn't match

Find out why an automation filter lets every record through or none at all, and how to test it with a manual run before you turn the automation on.

Written by Leo

Tip: Test before you turn it on. A simulated run skips the filter, so it can't test one. To test a filter, use Manual run on a test record and check the step And if the following conditions are met in the run. If the record doesn't match, no run appears. A simulated run does help with search conditions inside actions, such as Search for records. It runs them on real records without changing data, so a condition that finds too many records shows up early. Learn more about Test automations →

A filter compares a field with a value. Tape works out the value when the automation runs, so a filter that looks complete in the editor can still behave differently for a specific record. The situations below cover the most common cases.

An automation for Expenses in the editor. The highlighted filter row reads Where Approver Is Submitted by, so the value comes from a field of the record. The action adds the comment Please review this expense.

If the filter lets every record through

If your automation runs for records it shouldn't touch, the value in the condition may be empty. A condition with an empty value matches every record. When the whole filter uses And, every record passes and the actions run for all of them, without an error. The same applies to a search condition inside an action, such as Search for records. It then finds every record.

This can happen when the value is taken from another field, a variable, or the result of an earlier step, and that source is empty on the record. For example, the filter says Where Owner Is the Manager field of the record, but the Manager field is empty.

How to fix it

  1. Open the automation and check every condition that uses a record value.

  2. Add a conditional step in front of the action that checks the source isn't empty, or set a fallback value. Learn more about Conditional actions →

  3. Select Manual run, then select a test record where the source is empty. Check the result in the step And if the following conditions are met.

  4. Select Save changes.

To run an automation for every record on purpose, remove the condition. A filter without conditions always runs.

Note: This matters most before an action that changes many records at once, for example one that updates or deletes all records of a collection. It can change your whole database app and use actions for every record. Always test with Manual run on a test record after you add or edit a filter.

If the filter blocks every record

If nothing passes the filter, check each condition one at a time:

  • The operator: Is needs an exact match. For text, Contains finds part of a value. Learn more about Filter text fields →

  • The value: check spelling, spaces, and capital letters. For category and status fields, check that you selected the right option.

  • And or Or: with And, every condition must be true. If you want one of several conditions to be enough, select the word in front of the second row and choose Or (At least one filter must match). The choice applies to all rows of that list, so use Add filter group to combine And and Or.

  • A field that's empty: most options don't match an empty field, but Is not and Does not contain do. Use Is empty to check for an empty field, and Is not empty for a filled one. Add Is not empty if empty records shouldn't pass.

To find the condition that fails, remove all conditions but one, run Manual run on a test record, then add the rest back one by one.

If "Has changed to" doesn't match

The Has changed and Has changed to conditions compare the record before and after the update. They work with When a record is updated. A record that already has the value doesn't match, because nothing changed. For example, Status Has changed to "Approved" doesn't match a record that was already approved.

How to fix it

Use Is instead of Has changed to if you want to match every record that currently has the value. Learn more about Filter changes →

If the filter ignores part of a value

If a text filter doesn't find what you expect, check the field type and the operator first. Use Contains to find a word inside long text. A filter on a multi-line text field checks the complete text, without formatting. Is is case-sensitive, Contains isn't.

If a date filter returns the wrong records

  • Check which field the date filter uses. A calculation field that returns a date offers Is, Is not, Is before, Is after, Is empty, and Is not empty, plus Has changed with When a record is updated. Date filters work the same way on these fields as on date fields.

  • Check relative dates, such as Current date with + or - and an amount. Use Days for the amount. For one week, enter 7 days.

  • If a record has a date and a time, the time zone can move the date to another day. Learn more about Dates or times are off →

If a filter stops working after a field changed

A condition that uses a field that was deleted, or a value that points to a deleted field, no longer works. If a filter uses a deleted field, the automation is marked Broken.

How to fix it

Open the filter, select a field that exists in the condition, then select Save changes. Learn more about Active, paused, and broken automations →

Tip: Still having trouble? Ask in the Tape community.

Learn more

FAQs

Why did my automation run for all records?

If an automation runs for every record, it could be because:

  • The filter has no conditions.

  • A condition uses a value that was empty when the automation ran.

  • The conditions are joined with Or, so one match is enough.

Does the filter in the trigger work like a filter in a Conditional actions step?

Yes. Both compare fields with values in the same way. The filter under the trigger decides whether the run continues at all. A conditional step decides whether the steps inside it run.

Can I see why a record didn't pass a filter?

No. A simulated run skips the filter, and its step shows Skipped. Use Manual run to test a filter.

Why does a filter work in a view but not in an automation?

Views and automations both use filters, but an automation works out values when it runs. A value from another field or an earlier step can be empty for a record. Check the value with Manual run on a test record.

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?