elsa-workflows / elsa-workflows/elsa-core

http activity(flow) multiple input port error [BUG] [V3]

Open
#5,415 1 comment 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

I received an error in the sample workflow I drew in the image I added.
![elsaschema](https://github.com/elsa-workflows/elsa-core/assets/5259546/6b77fc1f-9251-48bc-aef3-5558f44e145c)

To summarize the error I receive, when there is more than one login to the http flow activity, it cannot redirect the unmached status on the previous activity's ports.
I have a process, this process makes a request. If this request receives the 200 http status code, it continues to port 200, that is, commit activity. If a different http status code arrives, it continues its rollback activity from the unmached status code port.
If the commit activity returns http code 200, it continues with success http response activity over the success 200 port. A different http status code other than 200 continues rollback activity from the unmached status code port.
If rollback activity returns 200, success http response is returned. But if a different http status code comes, error http response activity is called via the unmached status code.

In the logic I explained above, when a code other than process activity 200 http status code arrives, the unmached status code port does not trigger and the workflow remains at that step as suspended.
![elsa instance](https://github.com/elsa-workflows/elsa-core/assets/5259546/a7d5ef1d-ced6-4039-b769-4d15c2b7839f)

Elsa definition export file;
[sample-process-transaction (1).json](https://github.com/elsa-workflows/elsa-core/files/15376012/sample-process-transaction.1.json)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.