Improve FunctionExecutor error handling#3166
Merged
Merged
Conversation
alrod
reviewed
Nov 18, 2025
mathewc
force-pushed
the
log-exception-fix
branch
from
e773998 to
e1e0a3f
Compare
RohitRanjanMS
approved these changes
Nov 19, 2025
This was referenced Dec 3, 2025
Closed
This was referenced Dec 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses #3165.
For context, we had an Azure Functions bug where one of the registered loggers was throwing an exception. See Azure/azure-functions-host#11473. The test added in this PR simulates this.