Help

Upcoming database upgrades. Airtable functionality will be reduced for ~15 minutes at 06:00 UTC on Feb. 4 / 10:00 pm PT on Feb. 3. Learn more here

Automation Giving Error "Could not find matching rows for string" and also not pulling all fields specified

Topic Labels: Automations
Solved
Jump to Solution
818 3
cancel
Showing results for 
Search instead for 
Did you mean: 

Hello! I have an automation setup that when run “successfully” only populates some of the fields specified in the the action. Screenshot included below and highlighted where the errors are occurring. I also after a successful run initially eventually got an error message (seen in a screenshot below that “Could not find matching rows for string”. Was hoping could get some seeds of support on these two issues.

Results of Automation From Initial “Successful” Run (The column Tags__ForLinking is the target field that updates as a result of the automation):

image

Automation Setup:

Trigger:
image

Action:
(1) Properties
image
(2) Configuration
image
(3) Testing
image

1 Solution

Accepted Solutions

Solved… I think this error is a result of the “Generate a preview” functionality. When a latter step is being tested that relies on a value from a previous step that was ALSO only tested in “Generate a preview” option, it throws the error because there’s no actual data to pull from. The solution is to “Run as Configured” the preceding step for which the affected test is pulling a data value from.

It would be nice if the “Generate a preview” used data from previous “Generate a preview” values, but doesn’t look like that’s the case…

See Solution in Thread

3 Replies 3

Having a similar issue, same error message.

Having same issue, unclear what’s cause of error.

Solved… I think this error is a result of the “Generate a preview” functionality. When a latter step is being tested that relies on a value from a previous step that was ALSO only tested in “Generate a preview” option, it throws the error because there’s no actual data to pull from. The solution is to “Run as Configured” the preceding step for which the affected test is pulling a data value from.

It would be nice if the “Generate a preview” used data from previous “Generate a preview” values, but doesn’t look like that’s the case…