# Webhooks arrive in seconds

October 1, 2026 · Webhooks

Order events used to wait for a delivery pass that ran once a minute, so a webhook could reach you up to a minute after the order moved. They now go out as the order moves.

## What changed

- **Faster first attempt.** The first delivery of an event usually reaches your endpoint a few seconds after the order changes state. While Layout's delivery worker restarts it can still take up to about a minute.
- **Most events go out as the order moves.** A few, including `order.challenge` and some failures, are picked up by a background check that runs every few seconds instead, so they can take a little longer. If your endpoint is slow to answer and events back up behind it, a first attempt can wait longer.
- **Same retries.** The retry schedule, signing, headers and payload are unchanged.

## Why it matters

An integration that shows its own order status can now keep it close to what the order is actually doing, instead of a minute behind.

## What to do

Nothing. Deliveries can still arrive out of order or more than once, so keep keying on the order id and the event. `GET /v1/orders/:id` always has the current state.

## Breaking changes

None.
