elsa-workflows / elsa-workflows/elsa-core
[BUG]The call is ambiguous and matches multiple workflows( But actually there is only one workflow match the url is running)
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
## Description
The HttpEndPoint keep return **"The call is ambiguous and matches multiple workflows" error**.
But actually, there is only one instance is running.
1. **Detailed Steps**: Provide a step-by-step description of what leads to the bug. Be as specific as possible.
(1)Create a workflow with a HttpEndpoint to listen, for example, /test
(2) Run the workflow.There will be an Instance of this workflow running. Call from a client, it works.
(3) Stop and delete this instance.
(4) Edit the workflow, maybe to modify anything and run again.
(5) Call from a client, it prompt the "matches multiple workflows” error
2. **Code Snippets**: If the issue involves code (e.g., JavaScript error, server request failure), include the relevant snippets where the issue occurs.
There are two instances when the client call in, the source code to get the instances from bookmarks, you can see there are two.
But acctually, no matter from the elsa API or from the database, there is only one instance exists.
Contributor guide
Assessment
This issue has not been assessed yet.