AppSheet API Failure: No rows are present

[dbaum]

I'm battling various issues with a webhook task that invokes the AppSheet API. One is that it sometimes returns an error that "No rows are present". Any direction regarding troubleshooting is welcome.

My Start expression is simply a "[Related...]" virtual column that uses a REF_ROWS function to generate a list of key values. I confirmed precise spelling of the column names, as well as that the JSON syntax parallels other webhook tasks that do work as expected. The Bypass Security Filters? property is enabled for the automation's event.

Example of error from the app Audit Log

Step details from Automation Monitor showing row IDs can be referenced, but are not included in body of HTTP request to API

Rows section of body of HTTP request to API

[WillowMobileSys]

I ran into this issue with API calls when I had one step that created new rows and then a second step that depended on those rows.  One would think since these are processed on the server that once the first step was completed, those new rows would be available for any subsequent bot steps.  I found that NOT to be the case. 

Setting the steps to run Synchronously (Run Asynchronously is turned off) didn't work.  I tried Wait steps but that was before the recent issue was identified and fixed - they didn't help.  It may be that a simple Wait step fixes this for you now.

What saved me was the recently added "Trigger other Bots" setting within automation steps.  I split my Bot into 2 and have the first Bot result triggering the second. 

[dbaum]

Thanks. However, I think my situation is simpler and the complexity you note doesn't apply.

This is actually a standalone automation to change the value of some columns in existing records. A data change in a row in one table triggers the automation (which occurs reliably), and all the automation does is send this AppSheet API request to update the values of columns in related records in another table.  

[WillowMobileSys]

Understood, and I probably didn't explain well enough. 

When you get the "no rows are present" message, it is referring to your START expression in your API step.  It thinks there are no rows from which to operate on.  In your case, it thinks the Related column is empty.  

I am pointing out that If the Related column are rows that were just added into the app, then there is likely a timing problem where the API step is running BEFORE the Related column is fully updated on the server.

If your Related column has rows that have existed for some time before the API step ran, then you are experiencing a different problem.