Skip to content

Conversation

@wenjin272
Copy link
Collaborator

@wenjin272 wenjin272 commented Dec 29, 2025

Linked issue: #346

Purpose of change

Support retry/fail/ignore error handling strategy when chat occurs exception or response schema is not expected.

Tests

ut & it

API

No

Documentation

  • doc-needed
  • doc-not-needed

@github-actions github-actions bot added priority/major Default priority of the PR or issue. fixVersion/0.2.0 The feature or bug should be implemented/fixed in the 0.2.0 version. doc-needed Your PR changes impact docs. labels Dec 29, 2025
response, initial_request_id, model, messages, output_schema, ctx
)
else: # if there is no tool call generated, return chat response directly
_clear_tool_call_context(ctx.sensory_memory, initial_request_id)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we still need this when using sensory memory?

Comment on lines 252 to 254
tool_request_event_context = _remove_tool_request_event_context(
sensory_memory, request_id
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here. Since we're using sensory memory, do we still need to remove the context? This brings an extra memory update.

@wenjin272 wenjin272 force-pushed the support-chat-retry branch 5 times, most recently from ffeaf91 to ec29864 Compare January 5, 2026 06:28
[api] Move agent api to agnets module in java.

fix
fix

[plan] Refactor built-in chat action in java.
fix

[plan] Support error handling strategy for chat action in java.

modify default max retries

not manually clear sensory memory.

fix

fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-needed Your PR changes impact docs. fixVersion/0.2.0 The feature or bug should be implemented/fixed in the 0.2.0 version. priority/major Default priority of the PR or issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants