You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remote /health wait: count it against the command timeout and cap it #4567
#4541 made the remote /health check before the first send retry until the command's own timeout when the probe times out or gets a 5xx. That wait does not count against the command's timeout, and the send then gets its full timeout too. As a result:
A dead remote daemon that still answers (for example a gateway returning 502, or dropped TLS) makes every command wait up to its full timeout before failing: 90 s by default.
A command can take up to about twice its timeout.
commands.md documents this bound today, and the merged code reports details.healthRecoveryBudgetMs.
Required behavior
The /health wait counts against the command's own timeout. Create one deadline before the first probe, and give the send only what is left.
Cap the health wait at a few seconds by default, so a dead host fails fast while a restarting daemon still gets a short grace period.
A refused connection still fails at once, as it does now.
Completion
Tests: a dead host that answers 502 fails within the cap; a daemon that comes back inside the cap gets the command with the remaining time; a command whose budget ran out during recovery is refused with dispatched: no and never sent.
commands.md drops the "up to about twice the command timeout" bound.
The issue requests changing remote /health recovery behavior: count the health wait against the command timeout, cap it, and refuse sending when the remaining budget is too small. It includes concrete required behavior, completion tests, and documentation updates, so a maintainer can evaluate and implement it as an enhancement.
Activity
apex-sentinel-staging commentedon Nov 15, 2026
Apex Sentinel · Issue review
Suggested label:
featureThe issue requests changing remote /health recovery behavior: count the health wait against the command timeout, cap it, and refuse sending when the remaining budget is too small. It includes concrete required behavior, completion tests, and documentation updates, so a maintainer can evaluate and implement it as an enhancement.