[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)
Issue description
On rare occasions (it's not obvious what causes this), my container app job will continue to run even after completing the task. It runs until either it gets killed or reaches the timeout limit. This one completed the job successfully but got killed a minute later:
Console Logs
System Logs
In this other case, I had to stop the job manually:
Console Logs
System Logs
Steps to reproduce
Not able to reproduce, seems to happen randomly, I would guess <0.5% of the time.
Expected behavior [What you expected to happen.]
Container App Job shows 'Succeeded' and finishes, allow new queue messages to be processed.
Actual behavior [What actually happened.]
Container App Job doesn't completed, hogging the scaling rule and preventing new messages from being processed.
Screenshots
See above.
Additional context
I have another app job with almost identical code (regarding completion and resources) which has never had this issue. I can't figure out what is causing it.
This is an intermittent issue where the ACA Job's container exits but the execution still keeps on running. We have improved the logic for this specific case.
This issue is a: (mark with an x)
Issue description
On rare occasions (it's not obvious what causes this), my container app job will continue to run even after completing the task. It runs until either it gets killed or reaches the timeout limit. This one completed the job successfully but got killed a minute later:
Console Logs
System Logs
In this other case, I had to stop the job manually:
Console Logs
System Logs
Steps to reproduce
Expected behavior [What you expected to happen.] Container App Job shows 'Succeeded' and finishes, allow new queue messages to be processed.
Actual behavior [What actually happened.] Container App Job doesn't completed, hogging the scaling rule and preventing new messages from being processed.
Screenshots
See above.
Additional context
I have another app job with almost identical code (regarding completion and resources) which has never had this issue. I can't figure out what is causing it.