--- title: "A changed expiry applies within about a minute — qr3.app" description: "A changed, removed or newly set expiry now applies within about a minute instead of up to 24 hours later." canonical: "https://qr3.app/en/changelog/2026-09-expiry-within-a-minute-en/" lang: "en" --- # A changed expiry applies within about a minute — qr3.app > A changed, removed or newly set expiry now applies within about a minute instead of up to 24 hours later. Canonical: 2026-09 · Expiry # A changed expiry applies within about a minute September 29, 2026 api redirect A code can have an expiry (`expires_at`). After it, the code answers `410`. To keep scans fast, the redirect holds every code in a cache for up to 24 hours. ### What is fixed - **Changing the expiry:** a `PATCH` to `expires_at` now clears that cache. The new expiry applies within about a minute instead of up to 24 hours later. Before, a removed or moved expiry kept reporting the code as expired, and one set to now let it keep redirecting. - **Expiry at creation:** a code that expires within its first 24 hours now expires on time. - **Static codes:** a static code whose short link was opened sits in the same cache. Changing, pausing and deleting it now clear that cache too. - **Logo and a deleted code:** if a code is deleted while its logo is being uploaded or removed, the API answers `404` and no longer changes the deleted code. ### What you need to do Nothing. If you changed an expiry before this update, there is nothing to catch up on: the cache expires after 24 hours at the latest anyway. [Full technical documentation →](https://docs.qr3.app/en/changelog/) [← All entries](/en/changelog/)