> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/settings/notifications/notification-states.md). # Notification states Learn about the different states of a notification email. A notification is an email sent to users to inform them about events in their account. Examples include order status updates, subscription changes (upsizes or downsizes), invoice generation, and other relevant events. Notification emails can be in one of these states: **Queued**, **Discarded**, **Sent**, **Failed**, **Bounced**, or **Complained**. The following diagram shows the transitions between these states:

The state transition diagram of a notification.

The following table describes the different states:

State	Definition
Queued	The email has been queued for sending to the recipient.
Discarded	The email has been discarded because the individual or account has disabled the category, or the contact has placed an administrative block due to bounces or complaints.
Sent	The email alert is sent to the recipient.
Failed	The platform is unable to send the email message.
Bounced	The email message bounced and couldn't be delivered. This could be due to several reasons, including invalid email addresses, issues with the recipient's mailbox, and so on.
Complained	The recipient has reported the email message as spam or junk.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform.softwareone.com/modules-and-features/settings/notifications/notification-states.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.