Azure-docs: Core concerns not really addressed

[jrichview]

While it's great that you can do all this via the portal, your documentation depicts no code. It's unclear from the generated code when exactly the item is removed from the queue. How does one structure code that manages when and if a queue item is processed, particularly in terms of error/exception handling? These are the basic concerns that a function developer would want to see on this documentation page.

---

Document Details

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

• ID: af2152a5-8ed9-4006-6a86-3a59af0dab6b
• Version Independent ID: b2662f47-bc0e-c83d-38f2-cd9c880ea293
• Content: Create a function in Azure triggered by queue messages
• Content Source: articles/azure-functions/functions-create-storage-queue-triggered-function.md
• Service: functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[jrichview]

Sorry, I should not say it depicts "no code", but it only shows one line of code for logging that the function was called. It would have been clearer to say that the code does not clarify how to manage when/if a queue item should be removed from the queue. Presumably one would want to have the function code completed successfully before removing it from the queue.

[mimckitt]

Thanks for the feedback! We are currently investigating and will update you shortly.

[mimckitt]

Thanks @jrichview. The quickstart guides are designed to be very basic and to give a new Azure user a starting point into a particular scenario. Hence, many additional asks that some may have might be consider too complex for a quick start.

We do have some additional information for the bindings that functions uses when working with que storage:

https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-queue

I will assign this to the content author to review and see if and where we can improve this doc.

[ggailey777]

@jrichview, as @MicahMcKittrick-MSFT mentions these quickstart topics are kept simple "by design." They rely on code from the various trigger templates. It sounds like we need to do a better job pointing folks to more advanced topics after they complete these quickstarts?

[mimckitt]

@ggailey777 I think that is a good takeaway from here. We have seen quite a bit of feedback from the more advanced users so working towards implementing this might be beneficial.

[ggailey777]

@jrichview I think that the information you are looking for is documented here, and also in the Queue trigger article. As @MicahMcKittrick-MSFT points out, this is an entry-level article and we aren't supposed to distract customers with too much information. If you think that there is a discoverability issue around error handling, we can re-open this issue. Otherwise, #please-close.