---
schema_version: "1"
id: f5fe258ed5f1c6072fb67609f318813ee6bca85bbf7bb1abe6450008bbb77926
title: Configure Timeouts for Managed Omni Gateway
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/gateway/latest/managed-timeout.md
canonical_url: https://docs.mulesoft.com/gateway/latest/managed-timeout
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 57e3b9b5a13e37dba0b9acdd43f0effa9071e9d1e1ce34ccfb8c20660f217b96
description: MuleSoft Documentation Site
release: "1.14"
latest: true
---
---
product: Omni Gateway
version: 1.14
is-latest-version: true
---

# Configure Timeouts for Managed Omni Gateway

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Omni Gateway offers these timeouts to improve service quality and reduce computing resource waste:

- **Stream Idle Timeout**  
  The Stream Idle Timeout enables you to set a maximum amount of a time a stream can remain idle
  without receiving any data in either the inbound (client to Omni Gateway) or outbound (Omni
  Gateway to upstream service) direction.

  By default, all Omni Gateway API instances have a stream timeout of 300 seconds.

- **Upstream Idle Timeout**  
  The Upstream Idle Timeout enables you to set a maximum amount of time a stream between Omni
  Gateway and the upstream service can remain idle between requests.

  By default, all Omni Gateway API instances have an upstream idle timeout of 60 seconds.

- **Response Timeout**  
  The Response Timeout enables you to set a maximum amount of a time Omni Gateway waits for a
  response from an upstream service. The timeout time starts at the last request sent by Omni
  Gateway.

  By default, all Omni Gateway API instances have a response timeout of 15 seconds.

You can configure these timeouts for Managed Omni Gateway via:

- Managed Omni Gateway deployment: Set initial timeout values when you create the gateway.

- Runtime Manager runtime configurations: Applies to all API instances in the gateway after the
  gateway is deployed.

- Policy: Applies to one API instance or upstream and provides granular control.

## Configuration Precedence

When you configure a setting in more than one place, Omni Gateway uses the first value that is set,
in this order of precedence:

1.  **Policy**: A policy applied to the API instance.

2.  **Runtime Manager runtime configuration**: Used if no policy value is set.

3.  **Built-in default**: Used if neither of the other values is set. A policy value overrides the
    gateway-level value for the API instance it’s applied to. API instances without the policy use
    the gateway-level value.

## Configure Timeouts During Managed Gateway Deployment

Set timeout values in the deployment flow when you create a Managed Omni Gateway. For the UI steps
and parameter descriptions, see [Deploy a Managed Omni Gateway](https://docs.mulesoft.com/gateway/latest/gateway-managed-set-up).

## Configure Timeouts in Runtime Manager

1.  In Anypoint Platform, select **Runtime Manager**.

2.  Select **Omni Gateways**.

3.  Select your Omni Gateway.

4.  Open **Runtime Configurations**.

5.  Open **Timeouts**.

6.  Set values for **Stream Idle Timeout**, **Upstream Connection Idle Timeout**, and **Upstream
    Response Timeout**.

7.  Apply the changes.

## Configure Timeouts via Policies

Apply these policies to your API instance or upstream service:

- [Stream Idle Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-included-stream-idle-timeout)

- [Upstream Idle Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-outbound-upstream-idle-timeout)

- [Response Timeout Policy](https://docs.mulesoft.com/gateway/latest/policies-included-response-timeout)