Skip to main content

Hi Community.

Our MWO users are frequently getting the kind of failed transactions shown below, we are curious to know what could be causing this kind of failed transactions and what can we do to stop it? 

This is very inconvenient for the MWO users and frustrating.  Any input would be appreciated. 

  • ERRINV: Entity instance not found. (JT_TASK_CLOCKING - CLOCKING_SEQ=149977.0)

 

Thanks

Mesh 

Hello,

We have been experiencing the following error for over a year now and IFS Support have been unable to find the cause or a resolution:

Instance of entity JT_TASK_CLOCKING with primary key [xxx] not found in database.

I appreciate it is a different error to your post, but just wanted to highlight that we are suffering with failed transactions in similar area.

We are on Apps 10 Update 18.

Thanks

Shaun

@meshfemi we’ve been looking into very similar errors (more in line with what @SHAUN_KERSLAKE shared) for a while now but they have been very hard to recreate and therefore investigate. Can you report a support ticket on this please? Hopefully that will give us more insight on what’s going on here. Please remember to include device logs and other relevant information like device information, update level etc.

Thanks,

Rukmal

Reply


Terms & ConditionsCookie settings