Summarize dynamic DNS provider outages instead of showing raw responses

[drudge]

Requested by Nick · project thread

Before: when Cloudflare's API returned a 502, every configured record sent its own request in the same run, each one failed the same way, and the Dynamic DNS card showed every raw JSON body joined together. On a phone the text ran off the side of the card and pushed the facts grid out with it.

After: the first 429 or 5xx from a provider stops requests to that provider for the rest of the run. The card says something like home.penree.net A: Cloudflare had a temporary problem (502 Bad Gateway). Sable will try again. The redacted provider response is still available under View provider details, and the box wraps on narrow screens.

How

• dnsprovider.APIError replaces the formatted string error for non-2xx responses. It carries the status code and any Retry-After value (seconds or HTTP date), and Temporary() returns true for 429 and 5xx. Error() produces the same text as before, with the body collapsed to one line so a joined error has one line per record.
• dynamicdns: the record loop moves into publishRecords, which returns after the first temporary error from a provider. Other providers in the same run still publish. The next attempt waits for the longer of the existing backoff and the provider's Retry-After, capped at 30 minutes.
• Console: dynamicDNSErrorDisplay summarizes each line of the error. A 429 reads as rate limiting and a 5xx as a temporary problem. A 4xx keeps the existing "rejected the request: messages (codes)" summary, and other statuses fall back to "returned 404 Not Found". Records that failed the same way share one summary line, which names three records and counts the rest. MCP's last_error uses the same summary.
• CSS: .unifi-status > div gets min-width: 0, and the summary wraps anywhere and keeps line breaks.

go tool mage verify and gofmt -l . are clean. The new tests cover the APIError status and Retry-After handling, the provider short-circuit and retry timing, and the summary for Nick's actual error (four repeated 502 bodies), a 429, an HTML 404, a plain-text 403 with a token, and a mixed multi-provider error.

Screenshots are from a phone viewport (393px, dark) with the error from the report.

main	branch	branch, details open

The screenshots are added in one commit and removed in the next, so the squashed diff contains no images.

---

Generated by Claude Code