Hi @Hushan Hasarel,

What sort of infrastructure setup is involved here. Presume the mobile passes through some middle ware or firewall before being sent on to be processed in the database.

It would be best to trace this through that infrastructure as it looks like the thread it is being sent to is not expecting the mobile information.

Has this ever worked or is this a new setup?

Kind regards,

Lee Pinchbeck

Hi @Lee Pinchbeck 

Error occurs on random times and so far couldn’t recreate it on command. After the error occurs app continues working normally, aside from changes (transactions) not being saved on that moment. Apparently this has been working like this for almost an year, since the customer went live with FSM 5.7. Also, error only occurs on FSM windows mobile app.

Hi @Hushan Hasarel,

Do you have the other information I referred to on my previous post?

Kind regards,

Lee Pinchbeck

Hi @Lee Pinchbeck 

Still in the process of getting those information. I’ll keep you posted 

Thanks & best regards,

Hushan Hasarel

Hi ,

Can you please elaborate a bit more regarding the transactions that are not getting sync (Transaction types )? There could be so many reasons for this sync issue and This particular error message is new to my knowledge. May I know where did you notice such  error message? (Server logs or console or debug logs).

Would appreciate it if you can share that information as well, along with the exact function.

Best Regards,

Shageesha Prabagaran