Skip to content

fix(iisa): report IISA refusing a request apart from an outage - #761

Merged
MoonBoi9001 merged 5 commits into
mb9/refuse-unusable-per-chain-price-capsfrom
mb9/report-iisa-rejections-distinctly
Oct 27, 2026
Merged

MoonBoi9001 merged 5 commits into
mb9/refuse-unusable-per-chain-price-capsfrom
mb9/report-iisa-rejections-distinctly

Conversation

@MoonBoi9001

Copy link
Copy Markdown
Member

When IISA answers with a 4xx, dipper now logs the status and IISA's reply and calls the request refused, where it used to report IISA as unavailable with no reason given. The job still retries every 60 seconds, since a refusal is usually fixed by a deploy, and the outage breaker's log now names the chain whose pool lookup failed.

When IISA refused a request with a 4xx, dipper logged only the status and blamed an IISA outage.
It now logs the status and IISA's reply and says the request was refused, still retrying the job
every 60 seconds, since a deploy (new config, token or version) usually fixes a refusal.
The outage breaker asks IISA for each chain's pool of indexers, and when that lookup failed its
log did not say which chain, so a refusal tied to one chain's settings was hard to trace.
@MoonBoi9001
MoonBoi9001 added this pull request to stack #765 October 27, 2026 08:40
@MoonBoi9001
MoonBoi9001 marked this pull request as ready for review October 27, 2026 10:01
A refusal, such as after a token rotation or a version mismatch, stalls every reassessment
until someone deploys a fix, but nothing alerted on it. It is now one of the default alerts.
The comment said the trimmed body is at most 1,024 bytes, but a note giving the full length is
added after the cut, so the result can run a little past that.
@MoonBoi9001
MoonBoi9001 merged commit 4847399 into main Oct 27, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant