-
Beta Was this translation helpful? Give feedback.
Answered by
Suchiman
Dec 3, 2024
Replies: 1 comment 3 replies
-
I don't think that it makes sense, to have {CorrelationId} in the Url of an HttpEndpoint, that is set to trigger the workflow. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.