Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Reliability] Repeated tool-call errors (path/retry patterns) inflate latency; need stronger fail-fast + dedupe

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Repeated tool-call failures in a single turn can cascade into extra retries/attempts and significantly increase latency.

Error Message

  • repeated "tool returned error" in same turn
  • Error-class aware retry policy (non-retryable/path errors should fail-fast).
  • Duplicate-error suppressor within a turn.

Root Cause

Repeated tool-call failures in a single turn can cascade into extra retries/attempts and significantly increase latency.

Fix Action

Fix / Workaround

Observed symptoms (local logs)

Top tool errors:

  • terminal: 41 errors
  • read_file: 12 errors
  • search_files: 5 errors
  • patch: 4 errors
RAW_BUFFERClick to expand / collapse

[Reliability] Repeated tool-call errors (path/retry patterns) inflate latency; need stronger fail-fast + dedupe

Summary

Repeated tool-call failures in a single turn can cascade into extra retries/attempts and significantly increase latency.

Observed symptoms (local logs)

Top tool errors:

  • terminal: 41 errors
  • read_file: 12 errors
  • search_files: 5 errors
  • patch: 4 errors

Common signature classes:

  • path not found / bad path normalization
  • repeated "tool returned error" in same turn

Expected behavior

  • Error-class aware retry policy (non-retryable/path errors should fail-fast).
  • Duplicate-error suppressor within a turn.
  • Better remediation hints after first failure (especially path normalization on Windows).

Actual behavior

  • Repeated failures can continue in same turn, adding avoidable token and wall-clock cost.

Related existing discussions (possible overlap)

Why file this anyway

Even if some sub-problems are tracked, this is still reproducible in real usage and has high user-cost impact.

Environment

  • OS: Windows 11
  • Hermes profile: default

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

  • Error-class aware retry policy (non-retryable/path errors should fail-fast).
  • Duplicate-error suppressor within a turn.
  • Better remediation hints after first failure (especially path normalization on Windows).

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Reliability] Repeated tool-call errors (path/retry patterns) inflate latency; need stronger fail-fast + dedupe