Hi @Jusuf Ramic.
The python 139 error, there's a troubleshooting guide that you can take a look at. See Troubleshoot: python exited with code 139 for steps you can take to mitigate the issue. If none of them don't help, please do let me know.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
I'm currently working with a ~v4 Azure Function running on Linux, implemented in python 3.9 (using v2 programming model), which is triggered by EventHub. The function processes incoming payloads, performs transformations, and writes the data into an SQL Server database by executing stored procedures, using pyodbc
library.
Issue: Occasionally, the function fails in such a way that it restarts the host, bypassing the retry functionality. Looking at Application Insights, the failed invocation includes the message "Invocation cancelled - exiting retry loop". Sometimes this happens even after the function executes all steps successfully and prints the final log. This causes data loss when the failure occurs before the SQL Server procedure execution, since once the host restarts, the same event is not reprocessed. Of course, if the failure happens after the procedure execution, no data loss is observed.
Details:
pyodbc
to execute stored procedures)python exited with error 139 (0x8B)
Exceeded language worker retry restart count for runtime: python. Shutting down and proactively recycling the Functions Host to recover.
Hi @Jusuf Ramic.
The python 139 error, there's a troubleshooting guide that you can take a look at. See Troubleshoot: python exited with code 139 for steps you can take to mitigate the issue. If none of them don't help, please do let me know.