rahuldavisN Contributor.
Contributor.
350 views

An error occurred while debugging the flow - OO studio

Jump to solution

com.iconclude.dharma.runengine.RunException: Could not load the execution plan for the flow with UUID '1cd6ddaf-2e85-41f6-826e-5ac28fb9fb1f'.
at com.iconclude.dharma.app.debugging.EventDrivenDebugger.cleanupAfterFatalError(EventDrivenDebugger.java:1714)
at com.iconclude.dharma.app.debugging.EventDrivenDebugger$28.run(EventDrivenDebugger.java:1685)
at com.iconclude.dharma.app.util.ui.DharmaSwingUtils$4.run(DharmaSwingUtils.java:340)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:312)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at com.iconclude.dharma.app.util.DharmaEventQueue.dispatchEvent(DharmaEventQueue.java:123)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Caused by: com.iconclude.dharma.commons.exception.DharmaException: Could not load the execution plan for the flow with UUID '1cd6ddaf-2e85-41f6-826e-5ac28fb9fb1f'.
at com.hp.oo.studio.debugger.engine.controls.FlowExecutionControlImpl.play(FlowExecutionControlImpl.java:102)
at com.iconclude.dharma.runengine.debugger.RunControlImpl.play(RunControlImpl.java:410)
at com.iconclude.dharma.app.debugging.EventDrivenDebugger$19.run(EventDrivenDebugger.java:1221)
at com.iconclude.dharma.app.debugging.EventDrivenDebugger$18.doInBackground(EventDrivenDebugger.java:1144)
at com.iconclude.dharma.app.debugging.EventDrivenDebugger$18.doInBackground(EventDrivenDebugger.java:1140)
at javax.swing.SwingWorker$1.call(SwingWorker.java:296)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at javax.swing.SwingWorker.run(SwingWorker.java:335)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

0 Likes
1 Solution

Accepted Solutions
rahuldavisN Contributor.
Contributor.

Re: An error occurred while debugging the flow - OO studio

Jump to solution

content pack is not fully imported.

So deteled the entry from C:\Users\rahul\.oo opstudio.xml and reimpoterd the content pack.

This solved my issue.

0 Likes
2 Replies
Olman_Q_OO Respected Contributor.
Respected Contributor.

Re: An error occurred while debugging the flow - OO studio

Jump to solution

 Thank you for contacting Microfocus Forum. 

 My name is Olman, I am from the OO/CSA team. 

 Regarding your question, the only clue is "Could not load the execution plan for the flow with UUID '1cd6ddaf-2e85-41f6-826e-5ac28fb9fb1f'.". Please, check this flow UUID if the configuration inputs are fine, then my recommendation is to open a case with support in order to investigate in deep the cause providing the studio.log

Regards

 

Olman Guzman Quesada
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
rahuldavisN Contributor.
Contributor.

Re: An error occurred while debugging the flow - OO studio

Jump to solution

content pack is not fully imported.

So deteled the entry from C:\Users\rahul\.oo opstudio.xml and reimpoterd the content pack.

This solved my issue.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.