superfluous entity record update detected for 'Requests'

[Ralf Peters]

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

[Guest Chaz]

@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.

 

[Gary@ADL]

we have also seen this error,

[Ralf Peters]

just seem to start today , the user was resolving the call

[Guest Chaz]

@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.

 

[Ralf Peters]

only updated to your previuos version (816)  on friday

[Ralf Peters]

Hi,

we are now on Build 817 and it just popped up again

 

Thanks

Ralf

 

[Everton1878]

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

[Victor]

@Ralf Peters @Everton1878 looking into this...

 

EDIT: didn't forget about this, I am still investigating

[samwoo]

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

[Martyn Houghton]

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

[Tina.Lapere]

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

 

[Tina.Lapere]

@Victor - we are still getting this error.  Can you let me know if this is still being looked into.

Many thanks

Tina

[Victor]

@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...

[Tina.Lapere]

@Victor, OK great I just wanted to make sure it's being looked into.  I'll keep an eye out for updates.