# Message Events Message Events are the primary way to track the status of messages as they are handled by AMPS. Events are emitted by AMPS during message reception, processing, and archival. Custom statuses can be set by Python actions and services, however, the following are default statuses emitted by AMPS. ### Common Event Statuses * **Started:** Processing of the message has been started by a subscriber and the configured action will be performed on it. * **Completed:** Message processing has been completed and the action was successfully performed on the message. * **Retrying:** Message processing has been completed, the action was unsuccessfully performed on the message, and the message will be retried as per the subscriber's retry policy. * **Failed:** Message processing has been completed, the action was unsuccessfully performed and the message will not be retried either because the retry mode is **Never** or the retry limit has been reached. * **Terminated:** The session that was performing the message processing has been terminated and the message will not be redelivered. * **Terminated - Redelivering:** The session that was performing the message processing has been terminated and the message will be redelivered. * **Skipping:** A message that is retrying has been marked for skipping and will be skipped the next time it is processed by a subscriber. * **Skipped:** A message that was marked for skipping was processed by a subscriber and skipped, and will not be redelivered. * **Archiving:** Message archiving has been started. * **Archiving Failed - Retrying:** Message archiving has failed due to a communication error, archiving will be retried. * **Archiving Failed - Skipping:** Message archiving has failed due to a data error, archiving will not be retried. * **Archived:** Succesfully Archived the message. ### Grid Actions The following grid actions are available on the message events screen in order to perform certain management operations on messages. They can also be performed on many messages by selecting multiple messages and using the buttons to the right of the grid. * **Reprocess**: Reprocessing a message redelivers the message to the topic on which the event was emitted, allowing it to be processed again by any subscribers on the topic. * **Reroute**: Rerouting a message delivers the message to any topic. * **Skip:** Skipping a message tells a subscriber to skip this message the next time it receives it (i.e. It is retrying repeatedly due to an unfixable error). ### Message Details The message details screen is split into three tabs for convenience, **Message Details, Session History,** and **Message Preview.** #### **Message Details** The message details tab contains all the metadata for a given message. Any metadata values can be easily viewed or copied by clicking the metadata field. **Session History** The session history tab shows the list of sessions for the current message and any parents and children of the message. Clicking through the sessions shows any message events or logs emitted within each session. Double-clicking any message event navigates to that message event's details page. **Message Preview** The message preview tab contains a button to download the message data, and potentially directly shows a preview of the message if it is text, PDF, or a video. --- # 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.mftlabs.io/fundamentals/admin/monitoring/message-events.md?ask= ``` 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.