New Data Automation Triggered When Table Not Updated

[Dabu]

I have an app which collects data from users and inputs it into a table. When data is added to the table an automation is meant to trigger an email notification when a record gets added. Occasionally users submit information and get an email notification that there information was recorded but the data would not be found in the table or the version history of the table. How can the automation run if the table is not updated with their data?

My thought is that multiple people were submitting information at the time which was causing  records not to be saved as the table is a google sheet. The total user base for this app is about 7500. Does this seem like a possible cause? Are there any suggestions to resolving these issues?

[TeeSee1]

Start with checking the automation log. What does it say for the records that fired email transmission but not stored in the spreadsheet?

[Dabu · Accepted solution]

Hi TeeSee1,

I am unable to check the automation log and get the following message:

However, after creating a new automation which saves records into a separate google sheet records, missing entries in the primary google sheet now appear in this separate google sheet generated from the automation when the email notification goes out. So I think my problem is mostly resolved although I still am unsure what is causing the main table to have missing entries that the automation is catching.

[Steve]

---

@Dabu wrote:

My thought is that multiple people were submitting information at the time which was causing  records not to be saved as the table is a google sheet.

---

It's possible data could be lost if multiple users submit updates with the same row key. If that happens, the earlier submission will be replaced by the newer. Make sure your row keys are always unique. If you are generating your keys using anything other than UNIQUEID(), please share the expression so we can consider the risks you may encounter.

[Dabu]

Hi Steve,

I am not using UNIQUEID() however the row key is unique and based on an ID given to each user and their names. The issues is also occasionally occurring for those who do not share names with anyone else in the system and without saving any records with the name in the table.

[Steve]

---

@Dabu wrote:

however the row key is unique

---

I doubt it, but since you're unwilling to share the expression, I can't help you.