Ralf Peters Posted August 22, 2016 Share Posted August 22, 2016 I am getting a few of these this morning ? "superfluous entity record update detected for 'Requests' The primary record was updated but no data changes were applied " What is the Error here ?? Thanks Ralf Link to comment Share on other sites More sharing options...
Guest Chaz Posted August 22, 2016 Share Posted August 22, 2016 @Ralf Peters we're aware of this issue and we're just doing some more checks before we make it available. Has this error just started appearing or is it something that's been happening for a while? Just so you know, this happens when the request is being updated multiple times in the same second with the same information. Usually when we try to mark it as read/unread by the owner of the request. Your data is not affected in any way. Link to comment Share on other sites More sharing options...
Gary@ADL Posted August 22, 2016 Share Posted August 22, 2016 we have also seen this error, Link to comment Share on other sites More sharing options...
Ralf Peters Posted August 22, 2016 Author Share Posted August 22, 2016 just seem to start today , the user was resolving the call Link to comment Share on other sites More sharing options...
Guest Chaz Posted August 22, 2016 Share Posted August 22, 2016 @Ralf Peters very odd if you've just started seeing it today. There's a new version (2.30.5 - 817) in the app store now which prevents the duplicate update, let us know if you come across this again. Link to comment Share on other sites More sharing options...
Ralf Peters Posted August 22, 2016 Author Share Posted August 22, 2016 only updated to your previuos version (816) on friday Link to comment Share on other sites More sharing options...
Ralf Peters Posted August 24, 2016 Author Share Posted August 24, 2016 Hi, we are now on Build 817 and it just popped up again Thanks Ralf Link to comment Share on other sites More sharing options...
Everton1878 Posted August 24, 2016 Share Posted August 24, 2016 I've had this error today as well while updating a call, previously I'd only seen it when resolving/closing a call This is the first time I've seen it since we updated to the latest version Link to comment Share on other sites More sharing options...
Victor Posted August 24, 2016 Share Posted August 24, 2016 @Ralf Peters @Everton1878 looking into this... EDIT: didn't forget about this, I am still investigating Link to comment Share on other sites More sharing options...
samwoo Posted August 30, 2016 Share Posted August 30, 2016 Hi, We've been getting this issue for the last few weeks. It sounds like there are multiples of the same actions occurring when we press a button once, but throwing an error because the action has already been completed. There doesn't seem to be a pattern to it though. Thanks, Samuel Link to comment Share on other sites More sharing options...
Martyn Houghton Posted August 31, 2016 Share Posted August 31, 2016 We are seeing this error too, even though we have been on 2.30.5 - 817 since last Tuesday. As @samwoo indicates this it occurs even though you have only clicked on the action button once. Cheers Martyn Link to comment Share on other sites More sharing options...
Tina.Lapere Posted September 2, 2016 Share Posted September 2, 2016 We've just upgraded to 2.31.6 and I'm still getting the error message :-( Rather annoying as I was advised it was fixed. Tina Link to comment Share on other sites More sharing options...
Tina.Lapere Posted September 7, 2016 Share Posted September 7, 2016 @Victor - we are still getting this error. Can you let me know if this is still being looked into. Many thanks Tina Link to comment Share on other sites More sharing options...
Victor Posted September 7, 2016 Share Posted September 7, 2016 @Tina.Lapere yes, it is definitely still investigated. It has been reported in other instances as well. We still need to understand the circumstances when this issue occurs, unfortunately we could only identify a partial pattern that still does not replicate it 100%. We need to find this first otherwise our developers do not know exactly how to tackle this behavior... Link to comment Share on other sites More sharing options...
Tina.Lapere Posted September 7, 2016 Share Posted September 7, 2016 @Victor, OK great I just wanted to make sure it's being looked into. I'll keep an eye out for updates. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now