Azure 30 days challenge issue for Exercise - Create a workflow using Durable Functions

Nikita Netajirao Pawar 0 Reputation points
2024-04-02T17:18:28.8033333+00:00

I have followed all the steps mentioned here Exercise-4 Durable function however I am facing error when I call the client function through URL (followed mentioned instructions for the same)

Please check below error I'm facing-

NOTE-function version is -4 (default)

2024-04-02T17:17:20.396 [Information] Executing 'Functions.HttpStart' (Reason='This function was programmatically called via the host APIs.', Id=2555996a-c529-4a13-8ad4-762910d2953b)

2024-04-02T17:17:20.401 [Error] Executed 'Functions.HttpStart' (Failed, Id=2555996a-c529-4a13-8ad4-762910d2953b, Duration=5ms)Result: FailureException: Cannot read properties of undefined (reading 'extraInputs')Stack: TypeError: Cannot read properties of undefined (reading 'extraInputs')at Object.getClient (C:\home\site\wwwroot\node_modules\durable-functions\lib\src\durableClient\getClient.js:11:40)at module.exports (C:\home\site\wwwroot\HttpStart\index.js:4:23)at t.InvocationModel.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,559 questions
{count} votes

2 answers

Sort by: Most helpful
  1. anand 235 Reputation points
    2024-04-03T06:24:24.7066667+00:00

    Hi @Nikita Netajirao Pawar 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.

    1 person found this answer helpful.

  2. Myat Thu 5 Reputation points
    2024-08-22T05:35:41.8266667+00:00

    Does this solution still work ?

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.