Unfortunately I also regularly experience this error in various files and as yet have not found any answer to solve what is clearly a bug in FileMaker Go... It seems mostly to occur when iPad is put into standby and then powered back on after a few minutes whilst a file is open on FMGo.... My best fix so far is to make sure the file is closed and FMGo fully quit, ie tapping into the app switcher and swiping up and away FMGO when the file is not in use.
I do hope that one day this error is solved... please fix it FileMaker Inc if you can!?!
I went over every script and added commit. We will see if the user complaints will go down.
We also experience this problem on the iPad exactly as skywillmott has described.
Our solution is to logout and login.
I believe this is a known bug. Why it hasn't been fixed, I am not sure. I believe FileMaker Go thinks some cached user is modifying the same record that the user is modifying. I know I can delete a file from FileMaker go that has data. Then open the same file, but with a few changes and it will display the old record data unless I completely exit the app or shut off the iPad and turn it back on.
Ran into this issue too.
Apparently is a memory issue.
Closing all other apps resolved the problem for me.
I hope that FM will release an update soon to fix this annoying problem, among other compatibility issues with iOS 8.1