AZ 204 challenge Error on Module named create-long-running-serverless-workflow-with-durable-functions

Question

Dear Azure Subject knowledge expert,

I am doing Azure developer challenge (AZ 204). Although I followed the instructions on the portal it led to an error message. I retried it 5 times therefore reaching out to you. Please guide.

Module name: Create a long-running serverless workflow with Durable Functions

Error Name: 500 Internal Server Error

Step name: Verify that the durable functions workflow starts

Step numbers in which the error occured

3.Select the HttpStart function. The HttpStart pane appears for your function.

4.On selecting Get Function Url and copy the URL. Your URL should resemble the following example:

Scenario: When Durable HTTP starter's endpoint( url mentioned below) was triggered it led to the 500 internal server error

The url is https://fnapp-deepikalab-mslearn-mod5.azurewebsites.net/api/orchestrators/OrchFunction?code=US_lr5HdnBg93xIryrdzTZVKOI3Co2AYowIOYWIrSjFBAzFuF_hocA==

Please guide to debug. If you can join me in a Microsoft team's call and show how to figure out it would be great.

Also, I tried to debug with ChatGPT that had 2 suggestions. One to check the app version and second was to check the log.

suggestion1 was to check package.json. But I do not know how what to correct here. .

Suggestion 2 was to check log. So, I opened activity log in the function. But do did not know how to proceed.

Thank you,

Deepika

Answer 1

Hi rdp ,

Thank you for reaching out Microsoft Q&A forum.

I ran into the same problem as you did. So replicated the learn lab using Create your first durable function in Azure using JavaScript | Microsoft Learn as a guide in VS Code. When I attempted to debug, I received Worker was unable to load function OrchFunction: 'df.orchestrator is not a function' error message stating that the OrchFunction was not a function, even though everything was created successfully. I downgraded the durable-functions package to 2.1.4 it successfully ran locally. After that, I went back to the console in the sandbox and ran npm install durable-fuctions@2.1.4 and reran the HttpStart function URL. Low and behold, it successfully ran. Since this is node we're dealing, it could be an issue between the 3.1.0 and Node 18. I'll share this feedback with the team but for now, I suggest using 2.1.4 or trying using a different version of Node.

Feel free to contact us if you have any more questions. I hope the information we provided was helpful to you! If it was, please consider accepting the answer by clicking the Accept Answer/Upvote button. Your feedback is valuable and can assist others with similar questions. Thank you for contributing to improving Microsoft Q&A!

Thank you.