ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #cloudflare
Resource Limit Exceptions in Workers Cloudflare Workers enforce strict resource constraints on the standard plan, specifically regarding CPU time and the maximum number of subrequests allowed per invocation. While CPU time tracks active processing and excludes I/O wait, the subrequest limit acts as a hard cap on outgoing fetch() calls. When these limits are
Goal Determine how quickly a write to Workers KV becomes visible to subsequent reads served from a different Cloudflare edge location, and how this differs from the local development environment provided by wrangler dev . Constraints & Uncertainty Workers KV is documented as eventually consistent; a write may not be immediately visible across all edge lo
When a request matches both a DNS‑level Cache TTL setting and one or more Page Rules that also define a Cache TTL, the documentation states that the Page Rule value “takes precedence” for matched requests. However, it does not clarify the resolution order when several Page Rules match the same URL, nor whether the most specific rule, the first rule in the li
Cloudflare Load Balancing introduced cookie-based Session Affinity in version 1.3.0, generating an edge-managed _cf_affinity cookie to route subsequent requests to the same origin. The documented behavior indicates that Cloudflare does not propagate SameSite or Secure attributes from the origin’s Set-Cookie header to this affinity cookie, and the Load Balanc
I'm setting up Cloudflare Zero Trust in front of an internal admin tool served through a cloudflared tunnel, and I want most paths to require SSO login while a health‑check endpoint stays reachable without authentication. The Access policy types include Allow, Require, Block, and Bypass, and the documentation describes Bypass as letting matching traffic skip
Unresolved Decision on KV Namespace Rollback Safety Cloudflare Workers KV supports atomic writes within individual keys, but the platform does not provide built-in transactional rollback mechanisms for schema-level changes across namespaces. When modifying the structure or semantics of KV data through a deployment, the 'kv:namespace' binding in Workers does
Missing Replication Latency Guarantee Cloudflare Workers KV replicates writes asynchronously across edge locations after the originating data center acknowledges the put operation. Documentation indicates replication typically completes within seconds but does not publish a maximum propagation delay, percentile SLA, or programmable signal for global commit.
Goal Determine whether AbortController-triggered cancellation in Cloudflare Workers terminates all in-flight operations before the runtime timeout, or whether KV writes may complete after the threshold. The free plan enforces a 10-second CPU time limit; paid plans extend this to 30 seconds. The runtime does not expose a built-in cancellation mechanism; devel
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?