Can you recreate the issue in your QA or DEV environment?  (grab a recent DB backup and log in there as that same mobile technician).  Try clicking on the Refresh icon in the Calendar view to refresh the entire work list module then switch back to the Card View to see if that helps as a workaround in the meantime.  We had a similar issue reported that was fixed in the 15.4.1.0 Maintenance Release which was released a couple of weeks ago.  So if you can recreate it on your QA or DEV environment then apply the latest maintenance release and test again to see if it resolves the issue there.  If the problem still occurs after the new build is installed then log a support ticket for the issue and send us the environment connection details (URL/user/pwd/profile for both the back-end and mobile applications) so that we can dig into it further.

Hi Reid,

We’ve been able to reproduce it on the customer environment and identify that the orders are still on the mobile app (2e error) because of an error :

Then the first error occures.

Any advice ?

BR

Laurence

Hi,

After check it appears despite this error message, the Problem code is still active and not obsolete at all. Any help would be appreciated. 

Hi Laurence, can you retry uploading the screenshot?  They’re not showing so I can’t tell what the error message is.  Is the mobile update API failing processing on the back-end application?  (does it say “Transaction Failed” at the top?)  If so, check the Alliance Event Viewer log files on the server that is configured to process the mobile API’s for additional information.