bot populates field in google sheet but then deletes it

[NCBOM]

I have a couple of bots to create PDF files and then populate a field in the table with the path to that file.  I have an action that reads that path and opens the file.  One of them works just fine.  The other bot runs correctly, creating the PDF in the proper spot, and populates the field in the table with the path.  Something then reverts the contents of that field back to what it was prior to the bot running.  I can tell this from going to the Google Sheet and looking at the update history of that cell.  There are no other bots or actions that clear that field, and when monitoring the bot, the monitor steps are as they should be, indicating that the field has been populated and the bot ends. 

I've added an update to another text field in the table plugging in "test" as the text to insert.  It plugs in "test" to the field, and then updates the field to the contents prior to the bot running.  

I can't find what would cause that field to be cleared or changed back to the old state.  Again, I have another action/bot combination that creates a PDF and path for another purpose in the same table and it works great.  The Appsheet field settings are identical for the path fields for both PDFs. 

Anyone seen this before?  And how to fix it? 

Thanks,  Wick 

[Steve]

Hmmm... Similar to this complaint earlier today: Google spreadsheet (Automatic Randomly Deleted Cell)

[AleksiAlkio]

It sounds for some reason the value is calculated in the server side differently. Please send a support ticket, thanks.

[NCBOM · Accepted solution]

I chatted with Google on the issue.  He could reproduce the error in my app but could not determine why it was doing it.  I rebuilt the bot from scratch (not copying the old one) and it worked just fine, retaining the field information as it should.  Still no clue as to why it was failing.  

[NCBOM]

From Google help desk: 

To answer your query, old bots some time after the configurational changes in the tables stop working and show unexpected behaviour in the app. In such cases it is always best to create a new to check if error replicates.