Skip to content

Worker restart due to function timeout does not fail current executions #10936

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
satvu opened this issue Mar 20, 2025 · 0 comments · May be fixed by #10979
Open

Worker restart due to function timeout does not fail current executions #10936

satvu opened this issue Mar 20, 2025 · 0 comments · May be fixed by #10979
Assignees
Labels

Comments

@satvu
Copy link
Member

satvu commented Mar 20, 2025

When an execution times out and the worker channel restarts as a result (here), no exception is passed into the call to shut down the existing channel . This results in TryFailExecutions() exiting early, and mid-flight executions are not failed properly as the worker channel shuts down.

If a timer trigger function is mid-execution during a worker channel restart like this, this scenario is particularly bad because the timer trigger won't run again until the previous execution finishes (which in this case won't happen). This can be mitigated by restarting the app itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants