Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Artifact PublishArea: what it touches
ImprovementsKind: in v2.1.277,
ImprovementsSection of the release
What
Requests to the artifact database now retry automatically in a few situations:
When the gateway reports it is busy, the request waits up to a capped delay and retries once, reporting whether the retry succeeded (relay_busy_recovered) or was needed at all (relay_busy_retried)
When the server rejects "session hints" sent with the request, it retries once (session_hints_rejected)
Separately, failures where the relay is unavailable or not served are now recognized as distinct cases and surfaced with a dedicated error message instead of a generic failure.
Why
This makes artifact database requests more resilient to temporary gateway congestion and gives clearer error messages when the underlying relay simply isn't available, instead of failing outright or with an unhelpful message.
