# NousResearch/hermes-agent · 500/502 errors triggering fallback behavior

## Open now

- 0 issues, 1 PR open on GitHub.
- PR #32971: Enable fallback on 500 and 502 errors

These issues and PRs concern making 500 and 502 server errors trigger fallback logic in the error classifier and agent. The work involves setting should_fallback=True for non-validation 500/502 errors and advancing the fallback chain accordingly.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #32961: error_classifier: 500/502 server errors should default to should_fallback=True

## Prior & competing PRs

- **#32971: Enable fallback on 500 and 502 errors**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `agent/error_classifier.py`, `tests/agent/test_error_classifier.py`
- **#33106: fix(error_classifier): set should_fallback=True on non-validation 500/502 (#32961)**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#32971`, `#32961`

## Fix status

- No merged fix on record.
- Subsystem: `agent`