Workflows are keep loading and never open.

basantsoni
Kilo Guru

‎07-19-2018 02:04 AM

Hello Friends,

Need your help, we have move workflows in update set from dev to test environments. Once I tried to open those workflows in Test Instance, it’s keep loading and never open in Workflow Editor. And same workflows are working and opening fine in dev. Instances. I checked in logs and nothing is showing apart from below logs.

Child processor failed: java.lang.RuntimeException: java.lang.NullPointerException: com.glideapp.workflow.ui.WorkflowDiagramProcessor.process(WorkflowDiagramProcessor.java:141)

com.glide.processors.xmlhttp.internal.XMLHttpRequestExecutor.process(XMLHttpRequestExecutor.java:110)

com.glide.processors.xmlhttp.internal.XMLHttpRequestExecutor.process(XMLHttpRequestExecutor.java:76)

com.glide.processors.xmlhttp.AJAXXMLHttpAggregator.process(AJAXXMLHttpAggregator.java:70)

com.glide.processors.XMLHttpProcessor.processJavaAJAX(XMLHttpProcessor.java:151)

com.glide.processors.XMLHttpProcessor.process(XMLHttpProcessor.java:104)

com.glide.processors.AProcessor.runProcessor(AProcessor.java:483)

com.glide.processors.AProcessor.processTransaction(AProcessor.java:205)

com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:178)

com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:167)

com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:31)

com.glide.sys.Transaction.run(Transaction.java:2038)

java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

java.lang.Thread.run(Thread.java:748)

 

Please find screen shots as well. Appreciate your help on this.

find_real_file.png

 find_real_file.png

Regards,

Basant Soni

 

 

Preview file
99 KB
Preview file
15 KB
0 Helpfuls
  • 3,205 Views
6 REPLIES 6

Ct111
Tera Sage

‎07-19-2018 02:42 AM

Hi  basantsoni,

 

Have you used  gs.print anywhere in your script , if YES then you need  to change it to   gs.log  everywhere in script wherever it is kept ...  and try to find a field or method that is using glide because it's result might be causing Null pointer exception.

 

Mark my ANSWER as HELPFUL if it served your purpose.

 
0 Helpfuls

basantsoni
Kilo Guru

‎07-19-2018 08:15 AM

Hi, 

Thanks for your response, But there is no Print in our workflows. since those are working fine in lower instances. 

thx, Basant 

0 Helpfuls

Brendan Hallida
Kilo Guru

‎08-01-2018 06:04 PM

hrmm, I'm seeing this with 1 of my workflows which I have just imported...  did you find a fix for this by chance?

0 Helpfuls

Brendan Hallida
Kilo Guru

‎08-05-2018 05:37 PM

Found the answer to my problem, with the help of the HI support team.

It was found that one of the activity definitions was missing from one of my workflow activities.

you can find them here:

https://<yourinstance>.service-now.com/wf_activity_list.do?sysparm_query=&sysparm_first_row=1&sysparm_view=

the culprit had a definition missing.  In my case, it was a Query AD activity.

Once I added what workflow activity definition it was, the workflow was able to open!

Cheers, Brendan.