Open RainerAtSpirit opened 3 weeks ago
To address the issue described, where the ParentWorkflowInstanceId
is not being set correctly for child and grandchild workflow instances, it is important to first ensure that you are using the correct version of Elsa Workflows that supports the propagation of the ParentWorkflowInstanceId
. If the issue persists even after confirming that the correct version is in use, it may be a bug or a misconfiguration in the workflow definitions.
As a customer support agent, I would recommend the following steps:
ParentWorkflowInstanceId
. If not, consider upgrading to a version that does.DispatchWorkflow
activity is configured correctly to pass the ParentWorkflowInstanceId
.If you need further assistance with this issue, please provide additional details such as the version of Elsa Workflows you are using and any specific configurations you have made to the DispatchWorkflow
activities in your workflows.
This comment was generated by Glime.
Description
Based on a support request in discord https://discord.com/channels/814605913783795763/1230144500777746493
Steps to Reproduce
Using ootb server and studio 3.1.2/3.1.0 and create
Parent-child-grandChild-workflow-definitions.zip
Run the Parent workflow from Studio and check the WorkflowInstances table. The
ParentWorkflowInstanceId
is null for all instances.Expected Behavior
The
ParentWorkflowInstanceId
of