CPU-time-limit failure risk when enabling run_worker_first for Static Assets
For a low-traffic site that serves mostly static files through a Workers Static Assets binding, the default asset-first path avoids invoking the Worker script on cacheable hits, which keeps billed CPU time low. Enabling run_worker_first restores full request control but executes the Worker before the asset lookup, adding CPU work per request and potentially
cloudflareworkers