A saved quiz and an accepted email are different receipts

Draft • Research checked 4 October 2026 • AI-assisted DomDNA editorial content. No independent clinical review or publication is claimed. General education, not individual medical advice.

A result screen can say that your quiz was saved while also saying that the email could not be confirmed. That is not necessarily a contradiction. Saving an application record and delivering a message involve different steps.

The DomDNA preview checked at commit 015c7c1926731bfadfa6ede67d0e0b9f401f9674 distinguishes these states in src/pages/Quiz.tsx and src/pages/Results.tsx. This article explains the implemented messages; it does not report a live save, a real delivered email or deployment of the preview.

Read what the receipt confirms

In the checked client, a saving request is treated as confirmed only after the response passes the implemented success checks, including a saved indicator. A successful HTTP response alone is not the whole application receipt.

The MDN Response.ok documentation explains the HTTP success property. It does not guarantee that the requested business operation happened. The application must interpret its own response information.

The preview then distinguishes email accepted, email pending, email failed and saving without configured email confirmation. It also has a state for an unconfirmed save.

A clear status sentence should therefore preserve the noun: saved record, accepted email or unconfirmed save. “Everything worked” removes the distinctions that help a person decide what to do next.

Accepted is not the same as in your inbox

The SMTP specification describes mail acceptance and delivery responsibilities. Acceptance can occur before later delivery problems become known.

The delivery-status notification specification describes reporting delivery attempts and their status. These standards explain why a sending acknowledgement and eventual delivery are separate concepts. They do not certify this preview's email provider or your mailbox.

The checked Results message explicitly says that service acceptance does not guarantee delivery. A missing message should not immediately be interpreted as proof that the quiz was not saved.

Conversely, receiving an email does not mean a clinician has checked the result. The message concerns an educational quiz and the application's handling of it.

A hypothetical interruption

Imagine you choose to save, then lose connectivity before the response reaches the browser. This is an editorial example, not an observed transaction.

The client may be unable to confirm the save. That is different from knowing with certainty that no record exists. A careful screen says what it knows: confirmation was not received.

In the checked implementation, retry handling retains request information for the same submission context. This article does not independently verify the deployed server's duplicate-handling behaviour or promise that every interrupted request is recoverable.

The practical response is to use the relevant retry route with the same details if that release provides it. Do not repeatedly submit through unrelated forms or assume that changing your email will fix a network interruption.

Pending and failed need different wording

A pending state means the client is waiting for the email-service confirmation represented in its response. A failed state means the response indicated an email problem. Both can coexist with a confirmed saved quiz.

The preview offers a details-and-retry route for those email states. Read the displayed instructions before using it. A retry is not a guarantee of delivery, and this article has not sent a test message.

If a restored browser session displays an earlier status, it is the last stored response, not a fresh delivery check. That boundary matters if you return much later.

Do not send health answers in a public comment to troubleshoot a receipt. Describe the status wording and the release context without posting the answers or contact details.

What the result screen still provides

The checked preview lets the person read educational results even when a save or email operation is not confirmed. Those topics come from quiz answers, not a laboratory test.

This helps keep a technical problem from sounding like a health verdict. A failed message-delivery step says nothing about whether a suggested topic is clinically relevant, and a successful one does not validate it as treatment advice.

What you can do with this

Write down the exact status before retrying. Separate the question “Was saving confirmed?” from “Was email acceptance confirmed?” and from “Did I receive the message?”

The public quiz route is a learning destination, not evidence that this preview is deployed. Check the actual release and its messages rather than treating this source guide as a live transaction receipt.