// AI Platform Drift

Cloudflare Access infrastructure apps now enforce 24-hour session limit

Cloudflare developer changelog · published 2026-10-15 11:33 UTC
ACTION NEEDED VERIFY_ONLY LIMITSAPI
WHAT CHANGEDCloudflare Access infrastructure applications now enforce a configurable session duration, defaulting to 24 hours. Previously, sessions had no hard limit but were subject to Gateway connection limits at 10 hours. When the duration elapses, active SSH connections are closed and users must reconnect. The duration can be set via dashboard or API when creating or editing an application.
WHY IT MATTERSAny SSH sessions through Cloudflare Access that run longer than 24 hours will now be forcibly terminated. Long-running maintenance tasks, database migrations, or persistent tunnels that previously worked will break mid-operation. If a target matches multiple infrastructure applications, the shortest configured duration applies, which may be less than 24 hours.
WHAT TO DOAudit your infrastructure applications for any SSH workflows that run longer than 24 hours—database migrations, long-running scripts, persistent tunnels. Either redesign them to complete within the limit or explicitly configure a longer session duration in the Cloudflare dashboard or API before they break.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloudflare One, Access - Infrastructure applications support a configurable session duration
+https://developers.cloudflare.com/changelog/post/2026-10-14-infrastructure-ssh-session-duration/
+Wed, 14 Oct 2026 00:00:00 GMT
+
+Infrastructure applications now have a configurable session duration with a default value of 24 hours. You can set the session duration when creating or editing an infrastructure application in the dashboard or via the API.
+
+When the session duration elapses, any active SSH connections through that application will be closed, and users will need to reconnect. Previously, infrastructure applications did not enforce a session duration limit. Sessions could persist beyond 24 hours in some cases, but were never guaranteed beyond 10 hours due to Gateway connection limits.
+When a target matches multiple infrastructure applications, the shortest session duration applies.
+For more information, refer to Session duration.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew session enforcement mechanism changes SSH connection behavior and requires API/dashboard configuration decisions.
signalsnew feature: configurable session duration for infrastructure applications · default value specified: 24 hours · breaking behavior change: sessions now enforced to close at duration limit · previous behavior documented: no hard limit, but Gateway connection limits at 10 hours · API change: session duration now settable via dashboard and API · operational impact: users must reconnect after session expires
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)