Pause a gateway | Faustine Docs

A paused gateway refuses every call and keeps its APIs, keys, users and settings. Pause a gateway to cut off all clients at once, for example while you fix the API behind it. To cut off one client, revoke its key or user instead.

The switch belongs to the gateway, so it pauses every environment.

Pause the gateway

To pause a gateway:

In the portal, go to Agent Gateway and select your gateway.
Select the Settings tab.
Turn off the Published switch. Its label changes to Paused.
Select Save changes.

The badge in the gateway's header reads Paused, and calls are refused from that moment.

What a client gets

Every authenticated call to the gateway returns 503 with the error code gateway_paused.

{
  "error": {
    "code": "gateway_paused",
    "message": "Denied (gateway_paused): This gateway is paused by its owner",
    "requestId": "<REQUEST_ID>"
  }
}

Client	What it sees
REST	The `503` response on every operation.
MCP	The same `503` as an HTTP error on the MCP endpoint, on every request, including the ones that connect and list tools. The client cannot connect or run a tool until you resume.

A call without a valid credential still gets 401, as on a published gateway.

Each refused call is recorded in the Logs tab with the reason Gateway paused. The gateway's API reference stays online.

Resume the gateway

To resume:

In the Settings tab, turn on the Paused switch. Its label changes to Published.
Select Save changes.

The gateway serves MCP and REST again immediately. Nothing else is needed: URLs, keys, users and their sign-ins are the ones the gateway had before the pause. While a gateway is paused, its Overview tab shows a notice with Resume, which opens Settings.

Next steps

Delete a gateway: remove the gateway and its credentials for good.
Create an API key: revoke one key and leave the other clients working.
Gateway HTTP: every error code and its status.