ColType Entry could not be found

[Austin]

Does anyone have experience with this error? I have randomly gotten it before but only once every month or 2.

[Steve]

I would guess you removed a column from the table being updated, but that the user’s copy of the app hadn’t synced since and wasn’t aware the column was removed.

[Austin]

I have no touched this app in a few months now. It’s currently live and not being developed. The user is syncing and making other changes all the time in the same tables.

Seems very odd but I regenerated the table and it now has 71 columns. I believe this would have to do with an outside process we have running on top of our database added a column. It is one that is deleted in my testing database which is what we use for development of our app as well as for upgrading the live version when we make such column changes.

[Austin]

Today I got this same error again. 7 minutes later the same user in the same app same action had a success. I did notice that this error has occurred with the same key but once with 70 columns and a second time with 71 columns. I have tried regenerating the tables but the column count stayed the same.

[Steve]

Try deleting all unused columns from the spreadsheet, leaving only the spreadsheet columns used by the app.

[ballyhoo]

I'm not sure whether to start a new post or resurect this one but I'm getting this error while testing an action that's triggering a script to calculate the latitude and longitude from an address. The error is as follows:

Failed: Error: Internal Error: Row with key '026fd01d' not updated because a ColType entry could not be found for column 30. The ColType array contains 30 entries. Error: 'Set Column Values' Data action ''Set Column Values' Data action 'Action for Set Latitude Longitude'' failed with exception Internal Error: Row with key '026fd01d' not updated because a ColType entry could not be found for column 30. The ColType array contains 30 entries. .

I'm using a MySQL database and the app is working well in all other respects, I just don't understand this error message at all to be able to diagnose the issue!

[WillowMobileSys]

@Austin  @ballyhoo  @Steve 

Did anyone ever figure out what the issue was or how to resolve these errors?

I am having the same issue.  In my case, I am using Big Query and added a sheet-based table set as the child table to a pre-existing database table.

The automation throwing the error is calling a Google script and then attempting to update the Parent row that has a "Related" column - the column complained in the error.

What is extremely odd is that this automation has 2 steps of very similar steps to make 2 updates on the same row.  One succeeds just fine.  The second fails with the error.

Any hints on how to address before I spend hours on it??

[Austin]

I was never able to find a rhyme or reason for the error. My belief is that 1. this error message isn't the true/source error and 2. some internal state gets messed up and the app eventually resolves itself either automatically or being coaxed into fixing itself by the attempts to troubleshoot. 

[WillowMobileSys]

---

@Austin wrote:

the app eventually resolves itself either automatically or being coaxed into fixing itself by the attempts to troubleshoot. 

---

@Steve @Austin @ballyhoo 

Exactly what I have discovered.  The app seemed to magically fix itself earlier this week.  Today, I tested the automation by adding an additional step.  When it didn't work and I deleted that step, I again get the error message noted above.

It took 3 days for the app to "heal itself" before.  I can't wait that long.  If I have to, I'll remove the automation and add it back in again and hope that resolves it.

I will open a ticket to Support.  Did you happen to open a ticket previously?

EDITED:  FYI! I tried duplicating the automation as well as creating anew.  The issue still occurs.

EDITED 2:  One thing I didn't articulate above, is that when I started getting the message the second time, the failure happened on the first "SAVE" Step of the automation - not the second "SAVE" step like before.   I switched back to the original automation (which was just simply disabled) and the error again happens only on the second "SAVE" step.  So it would seem when the error occurs, it is specific to the automation.

[Austin]

I do not remember if I sent in a ticket but it is likely that I did. I was constantly bothering support back in 2020.  

[Steve]

I have no idea. 🙁 It's clearly an internals bug.

[mateo]

I am experiencing the same problem. The error says:

"Error: Row with key '7d5bf035-9fbe-41a7-9692-d3f9c433c1fc' not updated because a ColType entry could not be found for column 45. The ColType array contains 45 entries. ."

It always indicates the last column in the table. Tried that many times.
It seems to be a bug, has anyone found a solution for this?

[Steve]

Please contact AppSheet Support for help with this.