# Show Toast

## Overview

Use a toast message to confirm a user's action and provide feedback. Toasts are overlaid notifications that stack horizontally and can be dismissed by the user.

Use a toast for one of these types of responses:

* **`Info:`** Inform users that their actions have triggered a process, and they may have to wait for completion before proceeding.
* **`Success:`** Confirm a successful or completed action.
* **`Warning:`** Warning toasts inform users of potential issues related to their actions and guide them to prevent future problems.
* **`Error:`** Communicate an issue preventing a user from completing their current action and can be fixed within their current flow.

In general, use a toast interaction in response to user action. To decide whether you should use Toasts or another type of messaging, jump to Toasts vs. Alert Modal vs. Confirm interaction.

<figure><img src="https://2929066058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDL6JQuZArjJeQvX2ot4y%2Fuploads%2F8WPHu3JWqEITfLVESGrf%2FShow%20Toast%20Avonni%20Components.webp?alt=media&#x26;token=b98e1746-aace-451a-84bc-1170de4ce0f3" alt=""><figcaption></figcaption></figure>

## Specifications

<table><thead><tr><th width="214">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Title</strong></td><td>Text that will be displayed in the header.</td></tr><tr><td><strong>Message</strong></td><td>Main content message for your alert box.</td></tr><tr><td><strong>Variant</strong></td><td>Appearance of the alert modal. With or without a header.</td></tr><tr><td><strong>Mode</strong></td><td>Determines how persistent the toast is. Choose between <code>Dismissible</code>, <code>Pester</code> and <code>Sticky</code>.</td></tr></tbody></table>

### Mode definition&#x20;

* #### Dismissible

  * **Description**: Toasts with the **`Dismissible`** mode appears for a short period and then automatically fades away. Users also have the option to dismiss the toast earlier by clicking on it or the close button.
  * **Usage**: Use this mode for informative messages that are not critical to the user's workflow, allowing them to disappear without requiring user action, thus maintaining a smooth user experience.

  #### Pester

  * **Description**: The **`Pester`** mode keeps the toast on-screen for a longer duration compared to **`Dismissible`**, but it will eventually close after a set time. It does not require immediate attention and allows the user to continue their work, but it persists longer to ensure the user has ample time to read the message.
  * **Usage**: This mode is best for notifications that hold moderate importance, where you want to ensure that the user has seen the message but it is not urgent enough to interrupt their current task.

  #### Sticky

  * **Description**: Toasts set to **`Sticky`** mode will remain on the screen indefinitely until the user takes action to dismiss them. They will not fade away automatically.
  * **Usage**: Reserve **`Sticky`** mode for critical alerts that require user attention or action before proceeding. These messages are crucial and should stay in view until the user acknowledges them, ensuring the message has been noticed.

  <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.avonnicomponents.com/experience-cloud/properties-panel/interactions/show-toast.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.