1. Reference
  2. Limits

These are the bounds the service enforces today. They are engineering bounds rather than plan limits, and they can change while the alpha runs.

WhatBound
Schedule data65,536 bytes, as serialized UTF-8 JSON
One-shot delaySeconds1 to 158,000,000 seconds
Recurring everySeconds60 to 31,536,000 seconds
Delivery attempts per occurrence8, including the first
Idempotency-Key receipthonoured for 86,400 seconds
Occurrence and attempt historykept for 2,592,000 seconds
Callback request body a receiver must acceptup to 69,632 bytes
delivery.maxDurationSecondsup to 86,400 seconds