Workflow instance viewer activity badges don't update after resuming workflow for a suspended HttpEndpoint activity

[briannoyes]

Description

When I run a workflow definition from the designer that contains an HttpEndpoint activity, and that endpoint gets called, the badge icons on the upper right of the activities do not show execution even though the journal does.

Steps to Reproduce

To help us identify the issue more quickly, please follow these guidelines:

1. Detailed Steps: Provide a step-by-step description of what leads to the bug. Be as specific as possible.

• Import the attached JSON
  http-endpoint-test.json

• Run the workflow in the designer

• Using Postman, make a PUT request to the HttpEndpoint activity (substituting your run's workflow instance ID):
  https://localhost:57070/api/workflows/httptest?workflowInstanceId=6e60e98c700cd45f
  and the request body containing this JSON:
  {"HelloProperty": "Hi there!"}

• Note that the HttpEndpoint activity does not show a completed execution, nor do subsequent activities even though the journal shows that they were executed.

3. Code Snippets: If the issue involves code (e.g., JavaScript error, server request failure), include the relevant snippets where the issue occurs.

4. Attachments:
   http-endpoint-test.json

5. Reproduction Rate: Indicate how often the bug occurs when following these steps (e.g., "every time", "intermittently: about 50% of the time").

6. Video/Screenshots: Sometimes, complex behaviors are better shown than described. If you think a video or screenshots would help clarify the issue, please include them.

7. Additional Configuration:
   • Mention any specific settings, features, or configurations that need to be enabled or present to reproduce the issue.

Providing a comprehensive and clear description will greatly assist in diagnosing the problem quickly and accurately. If you're unable to share some of the requested information publicly, please note that, and we can arrange for secure information transfer.

Expected Behavior

Describe what you expected to happen.
I expect that each activity executed will show execution counts when they have been executed.

Actual Behavior

Describe what actually happened. Include screenshots, if applicable.
The HttpEndpoint activity shows suspended and subsequent activities show no execution count badge.

Screenshots

If possible, add screenshots or screen recordings to help explain the problem.

Environment

• Elsa Package Version: Specify the version. If you've cloned the repo, mention if you are using the latest source code from the main branch.
• Operating System: Include your OS version (e.g., Windows 10, macOS Big Sur, Ubuntu 18.04).
• Browser and Version: If applicable, include your browser and version (e.g., Chrome 92).

Log Output

Include any relevant log output or error messages that might help diagnose the issue.

Troubleshooting Attempts

Describe any steps you have taken to troubleshoot or resolve the issue yourself.

Additional Context

Add any other context about the problem here. This could include the frequency of the issue (e.g., intermittent, every time), conditions under which the issue appears, etc.

Related Issues

Link to any related issues here.

[glime-ai]

To address the issue you're experiencing with the HttpEndpoint activity not showing execution counts in the Elsa Designer, even though the journal indicates that the activities were executed, it's important to ensure that you are using the latest version of Elsa. There have been updates and bug fixes that may resolve this issue.

Here are the steps you should take:

1. Update Elsa: Make sure you are using the latest version of Elsa. If you are not, update to the latest version and test again.

2. Check for Known Issues: Review the Elsa GitHub issues to see if this is a known problem with a suggested workaround or fix.

3. Review the Documentation: Ensure that you are following the correct procedures as outlined in the Elsa documentation. Specifically, review the HTTP activities documentation to ensure your workflow is configured correctly.

4. Debugging: If possible, debug the workflow execution to see if there are any errors or exceptions being thrown that are not visible in the designer.

5. Community Support: If the issue persists, consider asking for help on the Elsa Discussions page on GitHub or on the Elsa Stack Overflow tag.

6. Report the Issue: If after taking the above steps the issue is still unresolved, report it on the Elsa GitHub issues page with detailed steps to reproduce, the version of Elsa you are using, and any relevant logs or screenshots.

Please ensure that you provide as much detail as possible when reporting the issue to help the maintainers reproduce and address the problem efficiently.

This comment was generated by Glime.