Orders in the console
The console has an Orders page. It shows every order your application's keys caused, in the environment you have selected, newest first.
What you see
- A row per order: when it was created, the restaurant, the number of items and the outcome.
- A filter by outcome: placed, awaiting confirmation, failed or canceled.
- The full order when you open a row: outcome, items, total, when it was requested, when it was placed, and why it did not complete if it did not.
Reasons are written for you, not for us: "Item unavailable", "Store not accepting orders", "Pickup slot expired", "Card declined" and so on. Every failed order on the page charged nothing.
Awaiting confirmation is not failed
When Layout cannot yet tell whether an order reached the restaurant, the page says Awaiting confirm and never shows it as a failure. Retrying an order in that state could place it twice. The same rule holds in the API, where the state is unconfirmed; see Errors and status.
Why it matters
Until now, seeing what your integration had done meant reading your own logs or calling GET /v1/orders/:id one id at a time. Now you can check a build from your phone in the time it takes to open a page.
Breaking changes
None. The page reads the same orders the API returns, and shows only the ones your keys caused.