I know why these happen, at least in my application, but is there a way to turn them off or change their behavior? They can become a nightmare.

Any help is very much appreciated,

Lucas.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/b2615b2f77f0054a5c05ee2c93f12e0f2ed9248e.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/b2615b2f77f0054a5c05ee2c93f12e0f2ed9248e.jpeg 2x" data-dominant-color="EAD3AC">

popup.jpg1024×71 15.9 KB

Hi Lucus,

In my application i have removed “error(e)” statement in all the catch blocks of my MWS code, so that i ll be not able to see the messages…
Hope this will be helpful.

Regards,
Sunil.

Hummm… you mean in the XXXView.java files?

I’m curious how this works since the code triggering the pop ups must be on the client side – since they pop up iff you’re offline.

Thanks man,

Lucas.

Hi Lucas,

For every view, we will be having source in the designer
their just try to remove error(e).

Regards,
Sunil.

These error indicate there was an unhanded exception during async request processing. Look for what kind of async requests you make and if they result in any errors (they can be reported in the MWS logs, but not always).

Oh yes, I know WHY they happen. That’s not the issue. I need to disable them or change their behavior. Sometimes the cause is out of my control but it effect is a major annoyance to the user. Is this possible?

How did you resolve? I have the same issue but delete all the error(e) lines didnt work. Google says the reason is synchronus calls but I dont find who is this synchronus call. Help pls

NetworkError
Failed to execute ‘send’ on ‘XMLHttpRequest’: Failed to load ‘https://procesosdesa.ine.mx:8585/meta/default/wm_xt_fabricfolder/0000018939?method=savetemppage’: Synchronous XHR in page dismissal. See Chrome Platform Status for more details.
Error: Failed to execute ‘send’ on ‘XMLHttpRequest’: Failed to load ‘https://procesosdesa.ine.mx:8585/meta/default/wm_xt_fabricfolder/0000018939?method=savetemppage’: Synchronous XHR in page dismissal. See Chrome Platform Status for more details.
at send (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:1438:13)
at klass.request (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:1449:1)
at klass.qexecute (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:8582:32)
at klass.queue (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:8566:6)
at klass.request (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:8550:3)
at klass.initialize (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:1403:6)
at klass.initialize (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:363:16)
at new klass (https://procesosdesa.ine.mx:8585/ui/dyn/general.js?l=es_MX&v=200818123223:56:17)
at https://procesosdesa.ine.mx:8585/wm_noodle/dyn/noodle.js?l=es_MX&v=200117133822:4696:1
at Object.requireScratch (https://procesosdesa.ine.mx:8585/wm_noodle/dyn/noodle.js?l=es_MX&v=200117133822:4176:7)