AppSheet Bot Embedded Email Failure: "Row Inaccessible or Not Found" Error on Data Update Trigger

Hi everyone,

I’m encountering a frustrating issue with my AppSheet bot that’s preventing embedded emails from being sent reliably.

Problem Description:

I have a bot configured to send an embedded email when data is updated or added in a specific table. The bot uses the updated row’s data to populate the email content (dynamic email). However, I’m frequently receiving the following error:

“Error encountered in step with name [Send Embedded Email for Approval]: The row used to populate the embedded app view (dynamic email) was either inaccessible or not found.”

This error prevents the email from being sent.

Troubleshooting Steps Taken:

  • Regenerated Schema: I’ve tried regenerating the schema, but the issue persists and seems to occur randomly.
  • Verified Row Existence: I’ve confirmed that the rows exist and are not being deleted between the data update and the bot execution.
  • Checked Security Filters/Permissions: I’ve reviewed security filters and user permissions, and they don’t seem to be blocking access to the data.

Suspected Causes:

  • Data Synchronization Issues: I suspect there might be a delay in data synchronization, causing the bot to attempt accessing the row before the changes are fully reflected.

Request for Assistance:

I’m seeking help in diagnosing the root cause of this error and implementing a reliable solution. I need to ensure that the embedded emails are sent consistently upon data updates.

Could anyone provide insights into potential causes or suggest troubleshooting steps? I’m particularly interested in:

  • Best practices for referencing the updated row in a data update triggered bot.
  • Strategies for handling potential data synchronization delays in AppSheet bots.
  • Any known issues or bugs related to embedded emails and data updates.

I have encountered the same issue and I solved it by changing the embedded appview.

1 Like

Please contact AppSheet Support for help with this.

1 Like

Thank you guys, I will contact appsheet support since this comes randomly and the bug cannot be readily identified

1 Like