EdgeKitConfigError

Thrown when the call is misconfigured and a retry will not fix it: no feature names or too many, or a 400, 401, 403 or 404 from EdgeKit (a malformed request, a wrong API key, an origin the site does not allow, an unknown site id). The message says which.

This is the only error the clients throw. A decision that could not be made comes back as an unavailable result instead, so the page still renders.