Brent Sickmiller

Same issue. We have an Azure function that runs every hour in East US region. It was running successfully until midnight UTC 2022-11-08. Now it's failing. Is anyone in a...

> Downgrading azure-functions to 1.11.0 is a workaround for now. > > `azure-functions==1.11.0` > > Add this to the requirements.txt and redeploy. This workaround worked for our function. Thanks, @CoAct-Atif!

> @BSickmillerArchaea - Can you please share the function name? https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately for us to investigate? > > /cc @gavin-aguiar (Reason='Timer fired at 2022-11-08T00:01:39.5694520+00:00', Id=dcf90174-94e4-45b7-9e40-2a4599a7261e) Is this enough information for you?...

I rolled back the `azure-functions==1.11.0` workaround to `azure-functions` in `requirements.txt` and set `PYTHON_ISOLATE_WORKER_DEPENDENCIES` to `1` in the Azure AppSettings as suggested by @MagnusWagner-WIT and things are still working as expected....

@lamym, no typo. We initially downgraded to `azure-functions==1.11.0` as suggested by @CoAct-Atif as a workaround to our function suddenly beginning to fail out of the blue. See thread further up...