Skip to content

HttpEndpoint keep showing error: "The call is ambiguous and matches multiple workflows." #6172

Answered by Suchiman
kfconeone asked this question in Q&A
Discussion options

You must be logged in to vote

It's fine to have a "non unique" / hardcoded url for the trigger of the workflow, as long as there's only one workflow waiting for it.
But, relaying from discord here, make sure there's no manually started instance of this workflow. If you manually start it, it would then suspend at the HttpEndpoint activity and then you have a workflow that wants to trigger on some Url and another workflow that has a bookmark on the same Url, which could cause this issue. So best to go to instances and remove all of them.

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@kfconeone
Comment options

@Suchiman
Comment options

Answer selected by kfconeone
@kfconeone
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants