Anchorage API reference
    Preparing search index...

    The fence could not be READ. Deliberately distinct from ExecutionFencedError: no state was observed, so nothing may conclude the deployment is open — which is why this carries the same 503 a refusal does and every request-path caller lets it propagate.

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    Constructors

    Properties

    reason: { code: "EXECUTION_FENCE_UNREADABLE" }

    An optional machine-readable reason, rendered into the response body alongside the message. DECLARED HERE rather than sniffed structurally at the mapper so the channel is part of the contract a subclass opts into, and so the mapper needs no import of any subclass to render it (see the header for why that import must not exist).

    status: 503

    The response status. 4xx/5xx only — see doErrorResponse.