Skip to main content
March 13, 2024
Question

Child Process stuck at start node

  • March 13, 2024
  • 24 replies
  • 0 views

Hi,

I am trying to use Start Process Smart Service to initiate processes conditionally. It is a MNI. Sometimes the process runs without any issue, however, sometimes the child process that was started gets stuck at start node without any errors in the instance. Does anyone have an idea regarding this? Any help is appreciated.

Refer the flow below :-

1st PM - the smart service runs as an MNI, triggers multiple instances

 

3rd PM - Review Process:
It gets stuck at start node or script task node and does not move forward.




Thanks

24 replies

venkatrea696188
March 13, 2024

We need to more details about your scenario . How you designed "MNI" Like How child processes starts?? All at once  or...& Design of Child process (Activity chaining...)

March 13, 2024

I have updated details in the post above [mention:5abb751204a145abaeb28c7bf620b9d5:e9ed411860ed4f2ba0265705b8793d05] 

stefanhelzle0001
March 13, 2024

How do you combine MNI and conditions?

Can you share more details?

March 13, 2024

Sure, let me try to put in more info.
Edit: I have added details in the original post above [mention:a11f77a729fb4db2af76b09948583328:e9ed411860ed4f2ba0265705b8793d05] 

konduruc733182
March 13, 2024

Please share the MNI Configuration tab and the Overall parent & child model screenshot or configurations if possible, would be great for our understanding.

varuntejg243705
March 13, 2024

Hi [mention:a2f856ba16614447b647ec1da77a6747:e9ed411860ed4f2ba0265705b8793d05] ,

I think you are using Activity Chaining between parent process nodes and start process smart service, and if the node execution exceeds 3secs, the chain will break and process will be in stuck state.

If the problem is not this, please share more info, what you are trying to achieve by the process.

March 13, 2024

That's insightful, will look into it.

jagadeshk779486
March 13, 2024

Might need more info to find out the exact issue in your case.

But please check your MNI configuration, if your MNI moves on after " The first instance is done", then there might be chances of ending all the other processes without any error before it completes, as the main process will end after the first subprocess instance is completed. If you have configured the terminate as end node.

If possible please share more information, to understand what happened in your case. 

March 13, 2024

This isn't the case, however let me try to put in more info.

Edit: I have added details in the original post above [mention:15e6926406e641dc990304baa037ca0f:e9ed411860ed4f2ba0265705b8793d05] 

jagadeshk779486
March 14, 2024

Hi [mention:a2f856ba16614447b647ec1da77a6747:e9ed411860ed4f2ba0265705b8793d05] ,

Just right click and restart the paused node "Get ICF Details", if it runs successfully, then the problem is not with the current process, probably with the parent processes configurations.

If this process gets paused again, then its due to the configuration in this process or due to its existing data. Then probably you can proceed with the further debugging.

Also check the tomcat-stdOut.log if you can get any insight from the paused node.

prakhars0731
March 13, 2024

may be it is more time to save the data

March 14, 2024

That's not it, we checked.

stefanhelzle0001
March 13, 2024

You are using terminate end events. That might interfere with child process execution.

March 14, 2024

I remember testing this in older version but did not face this issue. Does Terminate End Event terminate an asynchronous child process?

stefanhelzle0001
March 14, 2024

I suggest to give that a try, and remove the terminates.

September 20, 2024

Hi [mention:a2f856ba16614447b647ec1da77a6747:e9ed411860ed4f2ba0265705b8793d05] ,

Previously I'm also facing similar kind of issue.

Cause of Issue is swim line assignment is configured as  Run as whoever designed this process model than after I changed to Run as whoever started the process, at that time its working.

Just check the swim line assignment and configured correctly and start the process which ever node is struck.