Unify Logo Footer.svg
Platform Tools
Logo
Connection settings

Connection settings

Configuring how a connection behaves beyond its credentials.

Overview

A connection's Settings tab configures telemetry — the usage metrics collected for that connection. You can define custom metrics (name, what to measure, when to publish, tags, and histogram buckets) that feed observability dashboards. That's what lives on the tab itself; the connection's behavioral options — rate limiting and circuit breaking — are part of the connection's main form instead (see below).

Where: Connection › Settings

Screenshot TODO — Connection settings

Rating-limit a connection or protect it from a failing app

For connectors that support throttling, the connection's own form (the Details screen, where the credentials are) includes two optional policies:

  • Rate Limit Policy — cap how many requests the connection sends in a time window (requests per minutes/hours/days), so busy automations stay within the app's documented limits and don't get throttled or blocked.

  • Circuit Breaker — pause requests automatically when too many are failing or running slow (configurable failure-rate and slow-call thresholds), so a struggling app gets breathing room and your runs fail fast instead of hanging.

Most connections work fine without either; reach for them when an app has strict rate limits or is flaky. Set them when creating the connection, or later by editing it.

Where: Connection › Details (Rate Limit Policy / Circuit Breaker)

FAQs

Are there settings that apply to all connections?

Yes — the Connections manager has its own Settings tab (next to Connections and Insights) with global telemetry settings that act as the default metric configuration across all connections; a connection's own Settings tab overrides it for that connection. Viewing and editing the global tab requires the view settings permission for connections. Use the global settings to set a sensible baseline once, and per-connection settings only where a specific connection needs something different.

Where: Connections › Settings (global) vs Connection › Settings (per connection)