Isolated Process Azure function v4 with .net 6 fails on Azure but works local

We have a few Azure Functions developed using isolated-process in .net 5 and we are migrating to .net 6.

The migration worked without problems and runs perfectly local, but fails when deployed to azure. We are using Http, ServiceBus and Timer triggers and all fail the same way:

It shows an "Executing" log in the "Log stream", but after a few seconds it fails with "**[Error] Final functionDispatcher state: WorkerProcessRestarting. Initialization timed out and host is shutting down**". After that the host is restarted.

All functions fail the same way, but only when running on Azure. They work perfectly local and there are no other logs on Azure to find out what could be going on.


The app was not created from scratch, but was updated from the previous version to use .net 6 and updating/upgrading all required dependencies.

**Edit**:

Application Insights shows the following 2 error log messages, aprox. 50 seconds after any attempts:
**Final functionDispatcher state: WorkerProcessRestarting. Initialization timed out and host is shutting down** and **Did not find any initialized language workers**