[BUG] ParentWorkflowInstanceId is not working as intended about elsa-core HOT 1 OPEN

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:

1. Verify that you are using a version of Elsa Workflows that supports the propagation of ParentWorkflowInstanceId. If not, consider upgrading to a version that does.
2. Review the workflow definitions to ensure that the DispatchWorkflow activity is configured correctly to pass the ParentWorkflowInstanceId.
3. If the issue persists, it may be necessary to report this as a bug to the Elsa Workflows GitHub repository. You can do this by creating a new issue and providing all the relevant details, including the version you are using, the workflow definitions, and the steps to reproduce the issue.

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.

from elsa-core.