# fix\(provider-core\): a timed-out provider probe retries before the next periodic refresh \(\#7230\) · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/76db76f9d609a2ae839a635bf5df065c034f5c3c)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 76db76f9d609a2ae839a635bf5df065c034f5c3c

Requested commit: 76db76f9d609a2ae839a635bf5df065c034f5c3c

Commit: 76db76f9d609a2ae839a635bf5df065c034f5c3c

Tree: 70e382002a4fa893f19784f5aa8d09c3c55f8925

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(provider-core): a timed-out provider probe retries before the next periodic refresh (#7230)

A probe that reached the executable but got no verdict (Claude's
--version past its deadline, a crashed process) stayed authoritative as
an error until the periodic refresh, five minutes by default, or a manual
refresh. The managed provider now retries such a probe up to three times,
thirty seconds apart, through the existing demand-aware serialized
refresh path. A conclusive probe resets the budget; an exhausted budget
leaves the periodic refresh in charge, so a provider that keeps failing
is not probed without bound.

Inconclusive is a structural check on the snapshot (enabled, installed,
error status, unknown auth) rather than message text, so Codex's timeout
snapshot qualifies too and an unauthenticated verdict never retries.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

```

## Parents

- [d27a1adacfb4488cac6bcef5c1203bac561c3de8](https://git.cafe/pingdotgg/t3code/commit/d27a1adacfb4488cac6bcef5c1203bac561c3de8?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/76db76f9d609a2ae839a635bf5df065c034f5c3c?format=markdown)