# NousResearch/hermes-agent · Cron documentation on fallback provider behavior and recovery

## Open now

- 1 issue, 0 PRs open on GitHub.
- #39056: Docs conflict: do cron jobs use fallback providers?

The three members appear to concern documentation about how cron jobs interact with fallback providers: one issue raises a docs conflict, and two docs changes mention reconciling a summary table and scoping provider recovery to its trigger. The titles do not show what the correct behavior is or whether any change was merged.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 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.

## Open related issues

- #39056: Docs conflict: do cron jobs use fallback providers?

## Prior & competing PRs

- **#39189: docs(cron): reconcile fallback-providers summary table with cron beha…**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#32646`, `#63884`
- **#63884: docs(cron): scope Provider recovery to the actual fallback trigger; state update durability**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#120224`

## Fix status

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