Activity function doesn't send failure error code 137 running out of memory to orchestrator.

Question

When having a large input, the activity function fails with error code 137 running out of memory but it doesn't send the failure to the orchestrator function. Therefore, the orchestrator functions keep running. Failure also doesn't send to the logic app.

Note that I deployed my function on a premium plan EP3 which I have 14GB of memory. However, I only used about 2.5GB of memory as the Azure Function Monitor shows.

Answer 1

The error code 137 is usually caused by the operating system killing the Python process due to an out-of-memory error. According to the documentation, the Azure Functions platform has a service limitation that terminates any function apps that exceed the memory limit.

https://learn.microsoft.com/en-us/azure/azure-functions/recover-python-functions?tabs=vscode%2Cbash&pivots=python-mode-decorators#troubleshoot-python-exited-with-code-137

You can try to analyze the memory bottleneck in your function app by visiting the tutorial section in memory profiling on Python functions.

https://learn.microsoft.com/en-us/azure/azure-functions/python-memory-profiler-reference#memory-profiling-process

If you have already done that and the issue still persists, you can try to reduce the memory usage of your function app by optimizing the code, reducing the size of data structures.