What is Causing the Error "Google Sheets Row Number Cannot Be Read" in a Shopify Partner Workflow?

This topic was automatically generated from Slack. You can find the original thread here.

Hi all. Having an issue with a workflow that is finding google sheet rows and deleting the data in that row if they match an uninstall trigger within Shopify Partner for an application. It is flagging an error that Google Sheets Row Number cannot be read - although it works perfectly every time in testing. I’ve recorded a quick Loom for clarity - any help as to what is flagging this error and why they aren’t being deleted please. Thanks so much for any help!

Hello , thank you for the video.

Could you check if the value Input tab on your Google Sheet - Find Row is valid on event having error of the Inspector UI?

Maybe it is because the event you tested on Builder is different from the new event emitted.

Hey thanks for getting back to me. I am not exactly sure what you mean by “is valid on event having error of the Inspector UI?” but here’s some screenshots that may help.

The test event was a different event to the one actually executed at 8am today. However, it works for ANY test event I choose.

Here’s the input tab for the error:

Here’s the find row configuration, it’s using “myshopify domain” as the find function within column B

Here is one successful test I did 2 days ago before setting the workflow active (same configuration as above^):

, the root cause is the find_row action did not find the value you passed in (.e.g [befikray.myshopify.com](http://befikray.myshopify.com)).

So there’re 2 ways to solve this:

  1. On the failed event (with the email [befikray.myshopify.com](http://befikray.myshopify.com)), could you make sure that the value always exists on your Google Sheet?
  2. On your workflow, you can add a Filter action to stop your workflow if the find_row action find no row

Thank you for that Leo :smile:

I assume my entry missed the window for them to be put into the excel (every hour) hence maybe why it couldn’t locate them when it came to delete them.

Thanks again for being so quick to help :raised_hands: