elsa-workflows / elsa-core

A .NET workflows library
https://v3.elsaworkflows.io/
MIT License
5.88k stars 1.06k forks source link

[BUG] Nested Workflow Does Not Honor Logging Persistence Settings #5252

Closed sfmskywalker closed 3 weeks ago

sfmskywalker commented 3 weeks ago

When executing nested workflows, the logging persistence settings specified in the nested workflow are not being respected. This issue occurs regardless of the configuration set on the parent workflow or the 'workflow as activity' settings.

Steps to Reproduce

  1. Set up a parent workflow and a nested workflow.
  2. Configure logging persistence settings in the nested workflow to exclude certain log outputs.
  3. Execute the parent workflow that includes the nested workflow as an activity.

Expected Behavior

The logging for the nested workflow should adhere to the configured persistence settings, excluding specified log outputs as defined.

Actual Behavior

Logging from the nested workflow does not follow the persistence settings and continues to show excluded outputs.

Additional Information

This issue needs investigation to ensure that nested workflows correctly inherit and apply their designated logging settings.

glime-ai[bot] commented 3 weeks ago

To address the issue you're experiencing with logging persistence settings not being respected in nested workflows, it's important to first ensure that you are using the latest version of Elsa, as bugs and issues are regularly addressed in new releases.

If the issue persists after updating, you may need to manually verify the configuration of both the parent and nested workflows. Ensure that the logging settings are correctly set in the nested workflow and that there are no overriding settings in the parent workflow that could affect the nested workflow's logging behavior.

Additionally, you should check the Elsa GitHub issues and discussions to see if this is a known issue or if there have been recent fixes or workarounds suggested by the community or the maintainers.

If you cannot find a solution, consider opening a new issue on the Elsa GitHub repository with detailed information about your setup, configuration, and the steps to reproduce the issue. This will allow the maintainers to investigate the problem and provide a fix or guidance.

Remember to include detailed logs, configuration files, and any other relevant information that could help diagnose the issue when communicating with the Elsa community or maintainers.

This comment was generated by Glime.