Logo
Chain Engine

Chain Policies

Configure Chain Engine startup validation, auth, health checks, fallback, retry, and bandwidth behavior.

Policies decide how a saved chain behaves at runtime.

Chain Engine Policies

Balanced Policy

The default policy is policy-balanced.

SettingDefault
NameBalanced
Startup validationDisabled
Require authDisabled
Expected status200
Request timeout20 seconds
Connect timeout12 seconds
Health check interval20 seconds
Failure threshold3
Retry budget1
Fallback enabledEnabled

The default Balanced policy cannot be deleted.

Policies that are in use cannot be deleted. This keeps running or saved chains from pointing at a missing policy.

Policy Fields

FieldUse
Startup validationProbe routes before accepting runtime startup as healthy.
Require authProtect the local runtime endpoint with Basic proxy authentication.
Auth username/passwordCredentials local clients must present when runtime auth is enabled.
Probe URLTarget used for health checks.
Expected status codesSuccessful statuses for probes.
Request timeoutWhole request timeout for forwarded requests.
Connect timeoutDial and tunnel timeout.
Health intervalHow often routes are probed.
Failure thresholdConsecutive failures before route health changes.
Retry budgetNumber of alternate route attempts when fallback is enabled.
Fallback enabledAllows fallback routes when the primary route fails.
Bandwidth limitOptional runtime traffic cap in megabytes.

Runtime Behavior Controlled By Policy

FeatureDetail
Startup validationCan require a route to pass probes before the runtime is considered healthy.
Degraded runtimeIf primary validation fails but fallback works, the runtime can start in a degraded state.
Retry budgetLimits how many fallback route attempts can be made for a request.
Failure thresholdDetermines when a route becomes unhealthy after repeated health probe failures.
Basic proxy authUses local Basic auth and a ZeroTrace Chain Runtime challenge realm.
Bandwidth limitStops forwarding when the cap is reached and records a bandwidth notice/error.

When To Customize

NeedChange
Require local clients to authenticateEnable auth and set username/password.
Target-specific healthSet a target-specific probe URL and expected statuses.
Faster failure detectionLower timeout and failure threshold.
More conservative operationIncrease timeout or failure threshold.
Hard traffic capSet bandwidth limit.

Do not use a probe URL that only works from your normal IP if the point is to validate proxy-chain exit behavior.

On this page