29-07-22 07:19 PM
Answered! Go to Answer.
01-08-22 03:28 PM
Hi Cory,
Can you click on your Resource Group where your resources are located for this exercise and see if there is more than one Storage Account? I suspect you will see the Storage Account you created from following page 18 of the guide, and then there will be another Storage Account that you did not create. Try clicking on this other Storage Account > Queues and check if you have a queue full of items populated from the Function App.
If this is the case, I believe the root issue is that page 19 of the guide instructs you to leave all of the default settings in place when creating the Function App. However, there is a Hosting section during that setup that asks which Storage Account should be linked to the Function App. By default, it will create a new Storage Account, rather than link to your existing Storage Account. I would like to think Microsoft changed Function App deployment, but it very well may be a mistake in the guide that shall be updated regardless.
Let me know if my findings are consistent with what you are seeing in your Azure environment.
Cheers,
Charlie
Edit: The guide has since been updated (v1.0.1) to reflect this discrepancy around linking Queues and Function Apps: https://digitalexchange.blueprism.com/dx/entry/9648/solution/human-in-the-loop-processes-with-slack-and-azure
29-07-22 09:13 PM
01-08-22 03:28 PM
Hi Cory,
Can you click on your Resource Group where your resources are located for this exercise and see if there is more than one Storage Account? I suspect you will see the Storage Account you created from following page 18 of the guide, and then there will be another Storage Account that you did not create. Try clicking on this other Storage Account > Queues and check if you have a queue full of items populated from the Function App.
If this is the case, I believe the root issue is that page 19 of the guide instructs you to leave all of the default settings in place when creating the Function App. However, there is a Hosting section during that setup that asks which Storage Account should be linked to the Function App. By default, it will create a new Storage Account, rather than link to your existing Storage Account. I would like to think Microsoft changed Function App deployment, but it very well may be a mistake in the guide that shall be updated regardless.
Let me know if my findings are consistent with what you are seeing in your Azure environment.
Cheers,
Charlie
Edit: The guide has since been updated (v1.0.1) to reflect this discrepancy around linking Queues and Function Apps: https://digitalexchange.blueprism.com/dx/entry/9648/solution/human-in-the-loop-processes-with-slack-and-azure
02-08-22 02:15 PM