Normal delivery
The receiver works normally. Send one alert and follow it from start to finish.
Sets the receiver back to "Works normally" if needed, then sends one alert.
Send a practice alert to a test receiver, then follow how the sandbox delivers it, tries again when the receiver fails, and makes sure it is never processed twice. Every alert here is synthetic. New here? Try a guided scenario.
Compose an alert
Test receiver: Works normally (the default for a new session)The scenarios below can change this.
Guide
The receiver setting applies to your whole session. This page waits while other alerts are being delivered, but another tab using the same session could still send at the same moment.
Alert journey
Animations only illustrate what the delivery service reports. They are not real transmission timing. Turning them off changes nothing else.
Send an alert to see its journey here, step by step.
Your alert
Not started
Delivery service
Not started
Delivery tryNo try yet
AcknowledgementNo reply yet
Receiving system
Not started
Recent alerts
- Your alerts will appear here.
Try a scenario
Send a normal alert, or follow a short guide through a failure and its recovery. Guides never start by themselves, and each step waits for what the sandbox actually reports.
Recover from a temporary problem
The receiver rejects the first try. You restore it, and a scheduled retry succeeds.
Sets your receiver to "Temporary outage" for the whole session, then sends one alert. One step at a time.
Avoid processing twice
The receiver processes the alert but replies too late. A retry is recognized as the same alert.
Sets your receiver to "Processes, then replies late" for the whole session, then sends one alert. One step at a time.
Rescue a stopped delivery
Every automatic try fails. You restore the receiver and retry the delivery by hand.
Sets your receiver to "Temporary outage" for the whole session, then sends one alert. One step at a time.
Set the test receiver yourself
Technical details
This page uses the sandbox's public API on the same server. Every status you see comes from the API; nothing is simulated in the browser. The full reference is in the API documentation (OpenAPI specification).
Service status
Checks /health (the process is running) and /ready (the database is
reachable and migrated). Neither proves that the delivery worker is running.
Not checked yet.
Session summary
Start a session to see a summary.
How the demo session token is stored
Starting a session gives this tab an anonymous token that expires after 24 hours. It is kept in this tab's
sessionStorage: it survives a reload, disappears when the tab closes, and is never put in a URL
or shown on the page. Any script running on this page could read it, which is acceptable for a throwaway demo
credential with no personal data, but not for real accounts (those would use HttpOnly cookies).
The page loads only its own scripts and never inserts received text as HTML.