Azure-docs: Clarification on the exact URL needed to call the sequence

[steveculshaw]

Can we please clarify on the exact URL needed to call the sequence for the dummies like me :-)

In https://docs.microsoft.com/en-us/azure/azure-functions/durable-functions-sequence#run-the-sample it says POST http://{host}/orchestrators/E1_HelloSequence which I tried, and got a 404. It was only when I realised that the reference to {host} had to also include the api, i.e. https://mydurablefunction.azurewebsites.net/api/orchestrators/E1_HelloSequence

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3b6ce511-60d0-9d1a-cf6f-c955adeae20b
• Version Independent ID: 0da09c8f-0a2f-26e4-2948-fcb43f67e251
• Content: Function chaining in Durable Functions - Azure
• Content Source: articles/azure-functions/durable-functions-sequence.md
• Service: functions
• GitHub Login: @cgillum
• Microsoft Alias: azfuncdf

[cgillum]

Hi Steve. It sounds like your host.json file is missing the http/routePrefix setting which we include in the samples. You can find how we set this up in the HelloSequence sample here.

Can you verify whether this is the cause of your issue?

[steveculshaw]

Firstly, and most importantly ... many thanks for responding.

It was my bad ... I'd jumped into sequence at the Chaining page, and was going through the portal manually creating the functions.
Once I added the sample you pointed at to the host.json, the POST http://{host}/orchestrators/E1_HelloSequence worked fine.

The install page section for Azure Portal does indeed refer to calling POST https://{your function app name}.azurewebsites.net/api/orchestrators/HelloSequence

But I think there is a still an issue with the Chaining page as the first section is using C# scripting and the Portal, and I can't see any note on amending the host.json ... _but I'm an old guy, so did I miss that as well?_

[cgillum]

Thanks for pointing this out. You're right - this is confusing and we need to fix it to make it not confusing.

[leon-andria]

The example in this page is really useless.
If we follow the steps describe above and using the samples from Github, it will not run. There is a lot assumption...
First, why we need to return 202 status code ? and also, we never get the "Location" header ? where it's coming from ? Without saying the url http://{host}/admin/extensions/DurableTaskExtension/instances/96924899c16d43b08a536de376ac786b?taskHub=DurableFunctionsHub&connection=Storage&code={systemKey}.
What is systemKey ? ntohing descibing this query string.
If someone can update this doc, it would be great.

[vxnsbir1ugsp]

Why the method is POST instead of GET?

[cgillum]

@vxnsbir1ugsp POST is commonly used when a REST API has side effects, like creating or updating resources. In this case, the side effect is a creation of a new orchestration instance.

[SuttyHoo]

I am using Postman to run E4_SmsPhoneVerification.

context.GetInput(); (always returns null)
I have tried to populate the body with a phone number; (Raw + application/json or text) also used params (key-value pair without success).
What is the trick?
Thanks

context.GetInput() returns null

[craigcaseyMSFT]

It looks like this original issue has been addressed, so I am closing this. If there are other outstanding issues that haven't been addressed, please open a new issue to track, as this issue is >90 days. Thanks!