# fix\(provider-core\): a probe retry honors a disabled health refresh interval · pingdotgg/t3code

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

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

Visibility: public

Requested revision: ecb6f5f5143c5ddd52b4c0d48fd6db2d0e8aab70

Requested commit: ecb6f5f5143c5ddd52b4c0d48fd6db2d0e8aab70

Commit: ecb6f5f5143c5ddd52b4c0d48fd6db2d0e8aab70

Tree: cc280c8553d819f7a0c98884937de486b9c2c6c3

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(provider-core): a probe retry honors a disabled health refresh interval

A health refresh interval of 0 turns background provider refreshes off,
but the inconclusive-probe retry only checked refreshOnInterval, so a
provider whose probe kept timing out was still probed four times in the
first five minutes. The retry now decides under the refresh semaphore
right before probing: it checks the effective interval (including a
setting changed while it slept), and uses the failure count as a probe
generation so a manual refresh that ran meanwhile makes the queued retry
a no-op instead of a redundant probe.

Also corrects the comment on the retry delay: 30s is shorter than the
staged Claude probe and the ACP probe deadlines; overlap is prevented by
the semaphore, not the delay.

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

```

## Parents

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

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