Unverified50% confidenceFactExact time
ctx.waitUntil() has a 30-second wall-clock limit: after the Worker returns HTTP 200, background tasks are forcibly cut off after 30 seconds even if cpu_ms: 300000 is configured.
1
Sources
50%
Confidence
Long-term
Relevance
10/20/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedcron-job.org has a timeout ceiling of about 30 seconds per request, so the invoked endpoint must return quickly and cannot perform time-consuming tasks.72% similarUnverifiedThe demo output shows: requests spaced about one second apart rather than 0.5 seconds (Crawl-delay overrode the configuration), an exact 2-second wait on 429, a headless 503 getting about 1.1 seconds of jittered backoff, /private requests never leaving the local machine, and the last profile request hitting the daily cap midway through a retry.72% similarUnverified大多数服务商对Webhook回调有超时限制，通常为5-30秒71% similarVerifiedThe end-to-end latency of direct cellular connections must account for the additional ground gateway backhaul and core network processing, and the actual user-perceived latency is typically on the order of 100–300 milliseconds71% similarUnverifiedOn its first run, after backfilling history, the scorer identified 263 one-hour stalls and two eleven-hour stalls; on a second-pass check, agents were actually working during about 108 points' worth of one-hour waits and those points were refunded; the two eleven-hour stalls were kept (the audit role was idle from 08:47 to 19:46 while the queue piled up).70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1074443API
curl https://kongchang.com/api/v1/knowledge/claims/1074443MCP
get_claim(id=1074443)