Simon

As mentioned previously, I am already in contact with azure support.

Tried: - upping the "functionTimeout": "00:10:00", in host.json, since the randomness made me think of timeout / resource issues. No changes in behavior. Ran into two new bugs while isolating:...

I have isolated and reproduced reliably one of the vague errors listed above: `4:00:49 PM: Error: The operation was aborted.` This specific reproducible isolated case was fixable with: - `PYTHON_ISOLATE_WORKER_DEPENDENCIES:1`...

So, the above error ``` 2:39:54 PM ae-api-compute-secondary: Writing the artifacts to a Zip file 2:40:18 PM: Error: The operation was aborted. ``` came back when including further pieces of...

I have discovered a new non-reproducible randomly appearing bug: ``` 2:57:46 PM ae-api-compute-secondary: Starting deployment... 2:57:46 PM ae-api-compute-secondary: Creating zip package... 2:58:02 PM ae-api-compute-secondary: Zip package size: 180 MB 2:58:04...

So, I have solved the deployment issue as a final step, at least for me, by using a specific AUR and deploying from the terminal instead of the azure extension:...

Renaming functions is difficult in a large project, and I have not seen an official guide to it.

Can confirm original problem and solution. Still figuring out how to make the workaround persistent, and the specific problem. Absolutely nothing in any of the logs.