elsa-workflows / elsa-workflows/elsa-core

Issue with conductor "Events"

Open
#3,327 3 comments 0 reactions 0 assignees View on GitHub
bug triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

Hello and thanks again for developing ELSA.

I'm trying to use conductor activities but facing issues with Event activities. It seems that events do not unsuspend the WF after I send the POST request. Either I'm not sending something in the correct format or there is some bug. Here is an example (Running ELSA 2.9.0):

# Example: Event Stuck
![event_failure](https://user-images.githubusercontent.com/12515767/194716473-6b84d05b-aae2-4233-8a3e-335e063f4c7b.gif)

WF definition: inside the attached zip file
[testing-conductor-events.zip](https://github.com/elsa-workflows/elsa-core/files/9739671/testing-conductor-events.zip)

The curl command generated by Insomnia:

curl --request POST \
--url https://localhost:5001/conductor/events/DishesDone/execute \
--header 'Content-Type: application/json' \
--data '{
"EventName" : "DishesDone",
"Outcomes" : ["Done"],
"Payload" : {
"Performer" : "The Hulk"
},
"CorrelationId" : "da76a8adb9d5452089d6781eec3ddba0",
"WorkflowInstanceId" : "afb97138cc9e4e11a04e76d1ea9ee176"
}'

Thanks for your help :)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the event workflow from the attached testing-conductor-events.zip using the documented curl POST to /conductor/events/DishesDone/execute. Check whether the request format, correlation ID, and workflow instance ID match the workflow definition and whether the event unsuspends the workflow. Done means identifying and correcting the cause or documenting the required request format.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.