Skip to content

Conversation

@cho-thinkfree-com
Copy link
Contributor

Summary

  • return a descriptive fallback when ToolExecutionException#getMessage() is null or blank
  • include the tool name and originating exception type so downstream LLMs can detect failures
  • cover the new behavior with dedicated unit tests

Checklist

  • Signed-off-by line added to the commit (git commit -s)
  • Rebased on the latest main and squashed into a single commit
  • Unit tests updated to cover the new behavior
  • Build executed locally and tests pass

Testing

  • ./mvnw -pl spring-ai-model -Dtest=DefaultToolExecutionExceptionProcessorTests test

Fixes #4518

@ilayaperumalg ilayaperumalg added tool/function calling bug Something isn't working labels Sep 30, 2025
@ilayaperumalg ilayaperumalg added this to the 1.1.0.M3 milestone Sep 30, 2025
@ilayaperumalg ilayaperumalg self-assigned this Oct 1, 2025
@ilayaperumalg
Copy link
Member

@cho-thinkfree-com Thanks for the PR addressing the issue! LGTM

@ilayaperumalg
Copy link
Member

Rebased and merged as f2d57cc. Cherry-picked to 1.0.x as well.

@cho-thinkfree-com cho-thinkfree-com deleted the issue-4518-fallback-message branch November 3, 2025 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enhancement: Return fallback message when ToolExecutionException#getMessage() is null or blank

2 participants