Publishing
Set deployment expiration
Choose a TTL or fixed deadline when publishing, then manage that deadline before the deployment expires.
- Released
- Area
- Publishing
Set a deadline with --ttl or --expires-at when you publish or run flat deployment update. Use --no-expiry on signed-in deployments to remove a deadline. The CLI now reports each deployment's expiration time or never.
--ttl accepts positive durations in minutes, hours, or days, while --expires-at accepts a future RFC3339 timestamp with an explicit timezone. TTLs begin when the API processes the request, so upload time counts toward the duration.
Anonymous deployments retain their original one-hour maximum and can only receive a shorter deadline. Claiming removes the default anonymous expiration while preserving any deadline you chose. Signed-in users can add, extend, shorten, or remove expiration before the deadline.
Expired deployments stop serving and cannot be restored. Flat retains their identities and currently keeps their stored files pending separate cleanup support. Expiration changes may take up to 60 seconds to reach every edge.