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!