Please provide more details on the issue you are facing
1. Complete error message (it would be better if you can share a screenshot)
2. Is this issue occurring while calling the subprocess?
3. If you can share a couple of screenshots on the process design would be helpful
1. Fauld Detail:
<fault hasElementData="false" hasMessageData="true" name="fault" namespaceURI="http://schemas.active-endpoints.com/wsdl/screenFlow/2010/10/avosAutomatedStep.wsdl" rethrowable="true" source="/process/flow/scope[@name='procTodoAcknowledgement']/sequence/invoke[@name='procTodoAcknowledgement']" suspendable="true"><messageData name="automatedStepFault" namespaceURI="http://schemas.active-endpoints.com/wsdl/screenFlow/2010/10/avosAutomatedStep.wsdl"><part name="automatedStepFaultResponse"><aetgt:faultResponse xmlns:aetgt="http://schemas.active-endpoints.com/appmodules/screenflow/2010/10/avosScreenflow.xsd" xmlns:xsd1="http://schemas.active-endpoints.com/appmodules/screenflow/2010/10/avosScreenflow.xsd"><xsd1:code>correlationViolation</xsd1:code><xsd1:reason>No matching receive for operation "Initiate".</xsd1:reason><xsd1:details/></aetgt:faultResponse></part></messageData></fault>
1 of 1 people found this helpful
Please check if the subprocess is valid and if that is calling any other subprocess, make sure they are valid. I would suggest you publish all the subprocesses and parent processes again (You can make some slight changes to the subprocess like adding or updating the description and publish it)
1st publish the subprocesses and parent process
Let me know if that helps you
We did the same way as you mentioned like
1.Checking all sub process - all are valid
2.publishing all the sub process and main process
still we are facing this issue .
Hi team Verizon ,
Where are these deployed on ? Cloud or Agent or Hybrid ?