Exception "Did not find any initialized language workers" when executing dotnet-isolated workers

mintchocolate 20 Reputation points
2023-11-20T10:39:41.9333333+00:00

I am using dotnet-isolated workers with queue triggers in my function app. The function works fine when enqueueing messages slowly one by one, but this exception occurs when I put hundreds of messages in the queue storage in a short time. Any ideas on how to solve this issue? Thank you in advance!

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

Accepted answer
  1. MuthuKumaranMurugaachari-MSFT 22,321 Reputation points
    2023-11-21T19:15:27.7133333+00:00

    mintchocolate Thanks for posting your question in Microsoft Q&A. As described in this issue discussion, Did not find any initialized language workers error is a race condition issue which happens when the worker process starts/restarts.

    Have you reviewed logs in application insights for the function app? That would indicate little more insight about the cause of the exception. If it doesn't help, then I suggest opening a new issue in azure-functions-dotnet-worker repo (similar issues with this exception) with details such as function runtime, invocation ID/function app name, code snippets, full error message/exception including stack trace etc.

    The details will help our product team in investigating the backend logs and find the cause. I hope this helps and let me know if any questions.


    If you found the answer to your question helpful, please take a moment to mark it as Yes for others to benefit from your experience. Or simply add a comment tagging me and would be happy to answer your questions.

    0 comments No comments

0 additional answers

Sort by: Most helpful

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.