Azure-docs: Where is the human being part in the Human Interaction pattern?

[ericbrunner]

I read that article multiple times but can't find the human beeing part in the interaction on the serverless side. The user/client side is clear.

My Use Case:

I want to build a durable function that does a live manual (human beeing operator) approval of an uploaded image
in blob store and returns true if the human beeing operator marks the image as OK or false if its marked as Not OK.

The durable function would have to wait for a nee storage queue message the human beeing operator sent to the queue (either with inage validation OK or NOK), and return true or false back in the response.

---

Document Details

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

• ID: a0f57f10-3c91-d982-f37c-8612da2fa763
• Version Independent ID: 36e3f432-7727-fb63-2a40-0002ad4c8972
• Content: Human interaction and timeouts in Durable Functions - Azure
• Content Source: articles/azure-functions/durable-functions-phone-verification.md
• Service: functions
• GitHub Login: @cgillum
• Microsoft Alias: azfuncdf

[ericbrunner]

Now I understand that the mobile phone actor is the human interaction. A diagram would help a lot

[mimckitt]

@ericbrunner thanks for reaching out. If you find yourself having issue or want to continue this conversation please feel free to reopen and we can continue :)

[ericbrunner]

Yeah I would like to continue. Please add a figure/diagram that shows that use case. A picture says more than 1000 words :)

[mimckitt]

@ericbrunner I have assigned the issue to the content author to investigate further and update the document as appropriate.

@cgillum can you please look into this?

[ericbrunner]

Something like that from the overview would help with that sample

I did some extra work and have drawn a sketch of that sample as foundation for a clean diagram.

[cgillum]

Thanks for pointing this out, and for providing the diagram! We'll update the docs to make this more clear.

[MarkMcGee1]

Thank you for taking the time to share your product and documentation feedback with us. Your input is valued because it helps us create the right documentation for our customers. Due to the volume of issues in our queue, we are closing open issues older than 90 days. We hope to continue hearing from you. Thank you.

[ghost]

Updates to address this feedback can be found in this article: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-concepts#human. Basically, we added another code snippet towards the bottom of that section showing how the human-triggered event can be raised, along with a description.