Termination of Component Workflow
Today if a main workflow invokes a component workflow and the component workflow is terminated for some reason, then the component workflow does not return any status back to the calling workflow and the parent workflow keeps waiting forever. This is the case if the setting on the "Invoke Component Workflow" action is set to wait for component workflow to complete and wait for the outcome
There should be a way for the component workflow to return back the status in case it is terminated
The issue we currently have is the workflow engine does not send us any kind of event to indicate that the component workflow (or any workflow) has suspended meaning we can’t send any notification back to the parent workflow. We are currently talking with Microsoft to see if they can provide us the info we need, will update you once we know more..
been under review for over a year now.. are you all making any progress on this feature?
This would be great to have, seeing as there is no notice as to when or why the component fails and users are stuck waiting(indefinitely) for the nintex wf to complete, not great for visibility if they dont see the business benefit of having components.
Allan Helbling commented
I have 2 component workflows used in more than 200 workflows. It would indeed be a great help and I will allow me to get fewer support ticket on my side.
So, any update ?
Rick - Do you have any timeline on when this will be implemented? We have SharePoint Online migration starting shortly
Hey Rick - Do we have any update on this
Rick, This is a very important feature as we have few UDFs that we are planning to convert to Office 365 and we need some way for the component workflow to trigger any kind of termination status back to the calling workflow. Would appreciate if you can look into this
Vikrant Behal commented
This is much needed feature.