Skip to main content
Question

Spreadsheet row not found, but for no reason?

  • Oct 27, 2026 7:18 PM UTC
  • 18 replies
  • 78 views

Forum|alt.badge.img+2

I reached out to Zapier support a little while ago with this same issue and never found a resolution. Here is my basic workflow:

  1. Customer signs up for our program using gravity forms
  2. Customer added to our master student list based on the information from the gravity form
  3. Customer profile created in our scheduling system under the email that was used on the gravity form (to ensure that the email matches what can be found on the master student list spreadsheet)
  4. Customer must log in to the scheduling system to book with us using said email
  5. Once they schedule, Zapier is supposed to look up that email on the master student list, identify the row, and then update the start date

A few times now, in no specific pattern, there have been zap runs that are “safely halted” because no spreadsheet row could be found. But, the emails so match, and the row should have been found.

 

I have already checked the basics - there is no extra space anywhere, there’s no formula on the cell, there’s no weird formatting applied. Does anyone have any ideas?

18 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 4:17 PM UTC

Hi ​@Maddie Webb 

Check the timestamps on the Zap steps to see when they ran to make sure the order of operations happened as expected so that the email was on the spreadsheet to be found.

 

For us to have more info, post screenshots showing:

  • how your Zap steps are outlined and configured
  • an example where a record/row was not found

Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 4:24 PM UTC

Clients are given access to the scheduling link 24-hours to 1 week after sign up, so the order of operations is not the issue.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 4:47 PM UTC

​@Maddie Webb 

Without more context about how your Zap steps are outlined and configured along with example of a Zap Run data where there was an issue, it’s hard for us to evaluate and advise.


Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 6:25 PM UTC

 


Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 6:27 PM UTC

The above customer signed up for our program in June, and only just got started, so their email has been on our list for months. I tried to show that the emails match without giving away personal info. It is a simple zap with lookup spreadsheet row, update spreadsheet row steps. This has run about 500 times, and 10 of the runs have been “safely halted” for no reason. So, the zap is configured correctly. I just want to know why those 10 rows didn’t go.


WebhookEngineer
Forum|alt.badge.img+1

The June example makes signup timing a much less likely explanation. The 490 successful runs show that the workflow generally works, but they don't tell us whether these failures are specific to certain records or intermittent.

Are the ten missed emails grouped in one part of the sheet, or scattered among rows that were found successfully?

For one failed run, compare the lookup step's recorded input with the corresponding value in the sheet and the input from a successful run. Use the failed run's details rather than relying only on the current editor configuration, so you're checking what that execution actually searched for.

If those values match, test just the lookup for the affected email without rerunning the update. Keep the original failed-run details. Whether that same lookup fails again or succeeds now gives support a much narrower issue to investigate.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 6:46 PM UTC

​@Maddie Webb 
Screenshots do not show how the Zap steps are configured in the CONFIGURE tab while in EDIT mode.
Screenshots do not show the DATA IN/OUT for the Zap step with an error in the Zap Run.
 

Make sure you updated the GSheet steps to use the current GSheets Zap app version.

 

 


Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 8:16 PM UTC

The configure screenshot did not attach

 


Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 8:19 PM UTC

The failures are spread out in time and in position on the spreadsheet. I replayed one of the zap runs that failed and it was still safely halted.


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 8:22 PM UTC

​@Maddie Webb 

Help links for using GSheets on Zaps: https://zapier.com/apps/google-sheets/integrations#help

 

Things to check: 

  • Do a copy and ctrl find to make sure the values match
  • Make sure the spreadsheet has no filters applied to the data
  • Make sure the spreadsheet has no hidden columns/rows
  • Make sure the spreadsheet has no gap columns/rows
  • Check the mapped variable in the Zap step lookup value field has no leading/trailing spaces
  • Check the submitted lookup value has no leading/trailing whitespace
  • Check the expected matching spreadsheet cell value has no leading/trailing whitespace
  • Check the capitalization of the values trying to be matched
    • Either lowercase or uppercase the values

Forum|alt.badge.img+2
  • Author
  • Beginner
  • Oct 28, 2026 8:30 PM UTC

Yes, I have already checked these things, and went and checked them again. Non of them are the culprit


WebhookEngineer
Forum|alt.badge.img+1

Thanks for checking. Since that run still fails on replay, we have a repeatable example to isolate.

I'd try changing just the lookup value in a separate test copy of the lookup step. Keep the spreadsheet, worksheet, lookup column and all other settings unchanged, but replace the mapped email with a literal value copied directly from the affected spreadsheet cell. Test only the lookup, not the downstream update, and leave the live Zap unchanged.

If it finds the row, that points toward a difference in the incoming value or mapping. If it still misses, I'd focus the next check on the destination/search setup. Neither result proves the cause, but either narrows the next check without repeating the whitespace checklist.

Does that literal-value lookup find the row?


Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • Oct 28, 2026 9:41 PM UTC

​@Maddie Webb 

If you are looking to hire help for troubleshooting your Zap issue, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory


Since replays of the same run still fail, the problem is almost certainly in the data, not timing. One thing I’d check that isn’t covered above:

Invisible characters. In a spare column, put =LEN(A2) next to a failing email and compare it to the length Zapier shows in the run’s Data In. A difference of 1 usually means a non-breaking or zero-width space, or a pasted mailto: hyperlink. =CODE(RIGHT(A2,1)) exposes it (ordinary trim checks won’t catch these).

Longer term: normalize both sides (lowercase + trim) before the lookup, and route “not found” to a review tab plus an alert instead of a silent halt, so a missed lead is never invisible. Happy to look at one failed run’s Data In (redacted).


  • Oct 29, 2026 12:48 PM UTC

Try replaying a failed run. If it works, it’s timing: add a Delay before the lookup. Also lowercase/trim the email with Formatter.

 


SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • Oct 29, 2026 4:44 PM UTC

Hi ​@Maddie Webb! 👋

Sorry to hear of the trouble on this. I checked the support ticket and it seems like the lookup was matching on Student First Name as well as Parent Email. Is that still the case or is it only matching on the email address in the Parent Email column now? 

Also spotted our Support team suggested swapping the Lookup Spreadsheet Rows (Advanced) action for the Lookup Spreadsheet Row action, in case the issue is specific to that action. That might be it, but I’d suggest copying the Zap and changing the action in the copy to test it with one of the emails it couldn't find previously to see if it's then able to find it before adjusting that action in the Zap you've got running now.

If it works, after you update the action in the original Zap you wouldn’t be able to replay the halted Zap runs, but you could use those halted Zap runs as test records and test the Zap to have it search for and update those rows like it should have done.  

Let me know how that goes, want to make sure this gets sorted!


Forum|alt.badge.img+1

Hi ​@Maddie Webb 

I have checked the zap and found What's happening Your lookup step searches the sheet for a row where both the Parent Email (column Z) and the Student First Name (column K) match the values from your booking webhook. If no row matches both, the step stops the Zap by design, and that's the "row not found" you see. The step is set up correctly, and the values it searched for in the failed run look clean. So the likely cause is that the booking and the sheet don't have the same email or first name for that student.

How to check.

  • Open the failed run in Zap history, click the lookup step, and note the email and first name under Data in.
  • In your sheet, on the tab the Zap reads (the first tab, gid=0), search column Z for that email.
    • No row with that email? The parent booked with a different email than on your form.
    • A row exists but column K is different (e.g., a nickname on the booking vs the full name in the sheet)? The first name is the mismatch.
    • Everything looks identical? There may be a hidden character such as a trailing space. In an empty cell you can run =LEN(K2) and compare it with the visible length.
  • Repeat for two or three other failed runs to see whether they follow the same pattern.

Ways to fix it

  • Correct the name or email in the sheet, or have customers use the same details as on the form.
  • Match on email only and handle parents with several students afterwards: Find and update spreadsheet rows in Google Sheets.
  • Don't lose unmatched bookings: add a Filter or Paths so bookings with no match go to a "needs review" sheet or an email alert.

One important thing: your Zap has an unpublished draft with the lookup changed to a fixed value and the first-name condition removed. Please don't publish that draft, as it would update the same row for every booking.

If the email and first name match exactly and it still fails, reply here with a screenshot of the sheet row (columns K and Z visible, personal details blurred) and the lookup step's Data in, and I'll look further.

Thanks!


oliverwilliams

Hi Maddie. Gaurav nailed the main issue. Your lookup requires both the email and first name to match. If someone books with a nickname, the whole thing breaks even if the email is right. Match on email first, then check the first name in a later step if you still need to. Also, run a quick LEN check on both cells. A trailing space makes two names look identical, but the character counts won't match. Instead of letting the Zap error out on a miss, route those rows to a separate review tab so you can spot them fast.