elsa-core icon indicating copy to clipboard operation
elsa-core copied to clipboard

Activity Output issues after upgrading to 2.14.1

Open pablotola opened this issue 1 year ago • 3 comments

I upgraded to version 2.14.1 yesterday and now my activity outputs are not working anymore, is this a breaking change or a bug?

This is a screenshot of the output log of one of my workflows working fine before and after the upgrade.

image

Project packages:

image

pablotola avatar Mar 06 '24 23:03 pablotola

Based on the context provided, it seems that you are experiencing an issue with activity outputs not functioning correctly after upgrading to Elsa version 2.14.1. This could be either a breaking change introduced in the new version or a bug.

To determine the cause, you should:

  1. Review the release notes for version 2.14.1 to see if any breaking changes related to activity outputs were documented.
  2. Check the Elsa GitHub repository's issues section to see if other users have reported similar problems and if there are any suggested fixes or workarounds.
  3. If you cannot find relevant information in the release notes or issues, consider reporting the problem as a new issue in the Elsa GitHub repository, providing all the necessary details, including the screenshots you've shared and a detailed description of the problem.

It's also worth noting that Elsa is an evolving project, and as mentioned in the known issues and limitations, some features are still a work in progress or not yet fully tested. This could mean that the issue you're facing is a known limitation or an ongoing work that the Elsa team is already aware of.

If you have a backup or a way to revert to the previous version where your workflows were functioning correctly, you might want to consider doing so while you investigate the issue with version 2.14.1.

Unfortunately, without direct access to the release notes or the GitHub issues for the specific version you've upgraded to, I cannot provide a definitive answer on whether it's a breaking change or a bug. However, the steps outlined above should help you in troubleshooting the issue.

glime-ai[bot] avatar Mar 06 '24 23:03 glime-ai[bot]

There is a chance the change in output serialization was related to the following Pull Requests:

Hangfire Updates: https://github.com/elsa-workflows/elsa-core/pull/4214 https://github.com/elsa-workflows/elsa-core/pull/4428 https://github.com/elsa-workflows/elsa-core/pull/4298

@johnwc Any chance the above changes caused the reported issue?

JSON Serialization: https://github.com/elsa-workflows/elsa-core/pull/4430 https://github.com/elsa-workflows/elsa-core/pull/4441

@liuliang-wt Any chance the above changes caused the reported issue?

dwoldo avatar Mar 29 '24 18:03 dwoldo

Unless this is a new activity that I am not aware of, there is no Hangfire Job Done Activity in Elsa. That sounds as if it is a custom activity. Sharing a small screenshot doesn't really allow us to help much.

johnwc avatar Mar 29 '24 19:03 johnwc