-
Notifications
You must be signed in to change notification settings - Fork 322
Exercise 6 Task 3: Cosmos DB trigger function Error #19
Comments
@kylebunting |
@snpdev, I was unable to reproduce this issue while testing and doing the latest update. The issue you referenced in the docs appears to have been resolved, so maybe this is no longer an issue? I'll continue to monitor, and if the issue appears, I'll add a note into the lab about steps to mitigate based on your instructions above. |
@kylebunting I have the issue replicating even after setting node version 8.11.1 please let me know any details you might need to get this issue resolved |
@A142838, I have still not been able to reproduce this issue. Could you check to see what the runtime version of your function app is on the Function app settings page? Also, could you try deleting your function app and recreating it to see if the error goes away? I have now run through this several times, and I don't get any errors creating the functions. |
@A142838, correction to the above. Just after I posted the comment, I got the error. Updating the node version to 8.11.1 worked for me, but I'll dig in further to see if I can do anything to get rid of the error. I'll also add a note in the steps on how to update the node settings, should anyone else get the error. |
@kylebunting Thanks for help in replicating the issue I have the issue even after setting the node version to 8.11.1 but the issue but once I restart after deployment in my CD pipeline it is fine. Also, the other thing is in the process explorer the node language worked process does show up but looks like it crashed soon after and the function app then just keeps returning 500. |
I've added a note into the workshop HOL on how to address the issue. This appears to be a bug with the node language worker process, so I'm closing for now, but will continue to monitor and add in corrections as the issue is addressed. |
In Exercise 6, Task 3 - Upon creating the Cosmos DB trigger function, the following message is displayed:
To resolve the problem I followed the instructions at MicrosoftDocs/azure-docs#17295, namely to change the Application Settings, WEBSITE_NODE_DEFAULT_VALUE value from 10.14.1 to 8.11.1.
I recommend that a note be added to the step by step instructions.
The text was updated successfully, but these errors were encountered: