Scenarios you can run

Run reseat serve --demo to press these. This page shows one result.

Each one makes something happen at the fake AWS, the way the real one can during re:Invent, or moves the demo clock. re:Seat reacts as it would for real.

Seats

• A seat opensSomeone cancels a seat in SVS306-R, a talk you rank above CMP409-R, which you hold at the same time.
• The new seat fills mid-swapYou approve that swap, and in the same second someone else takes the new seat.
• AWS adds a repeat sittingAWS adds another sitting of AIM310, a talk you want.
• A seat opens that clashesA seat opens in BIZ108, but it is at the same time as COP301, which you rank higher.
• A booking cannot be confirmedAWS says yes to a booking, but your schedule never shows it.
• A swap offer is about to lapseA swap waits for you, and you have not answered. The demo clock jumps to 2 minutes before it lapses.
• Your exact sitting is full, another has seatsYour rules allow only the ARC306 sitting you picked, and it is full. AWS adds another sitting with seats.

Your schedule

• A held session changes roomAWS moves CMP303, which you hold, to another room.
• AWS removes a held sessionAWS drops SEC351, which you hold, from the catalog.
• AWS moves a session too close to anotherAWS moves API319 to start ten minutes after CMP409-R ends, two venues apart.
• Your leave-now blocks go out of datere:Seat wrote leave-now blocks into your schedule. Then AWS moves ARC302-R half an hour.

On site

• Jump to the next morningThe demo clock jumps to 07:00 on the next conference day.
• Jump to 10 minutes before you leaveThe demo clock jumps to 10 minutes before your next leave time.
• Jump to the next leave timeThe demo clock jumps to when you must leave for your next session.
• Jump to a wanted session about to startThe demo clock jumps to 20 minutes before a talk you want but hold no seat for.

AWS and the network

• AWS switches writes offAWS stops accepting bookings for a while, as it did before 8 October.
• AWS switches writes back onAWS accepts bookings again.
• The API goes down for 11 minutesAWS's API stops answering for 11 minutes.
• The API comes backAWS's API answers again.
• AWS serves an empty catalog, then restores itAWS serves no sessions at all, as it did on 8 October, then fixes it.
• Your sign-in expiresYour AWS sign-in runs out.
• Sign in againYou sign in again.