All activity tab
Overview​
The All activity tab on the AI Assistants page shows recent events across your AI assistants in one chronological list, with the newest event first. Use it to track when assistants start, stop, wake, sleep, and encounter errors without opening each one.
To open this tab, click Assistants in the left navigation and select the All activity tab:

| Element | Description |
|---|---|
| [1] Search | Filters the list by assistant name, event type (for example, wake or error), or trigger type (for example, manual or user_message). The match is case-insensitive. |
| [2] Time range | Limits the list to a time window: Last 24 hours, Last 7 days (the default), Last 30 days, or All time. |
| [3] Download | Downloads the events currently shown as a JSON file. |
| [4] Activity row | An event shown as a row. See Activity rows. |
The list updates as you search and as you change the time range:
- The tab fetches up to 20 of the most recent events from each assistant, for up to 20 assistants.
- Search and the time range apply only to the loaded events, so All time shows all loaded events rather than your full history.
- If you have more than 20 assistants, the tab shows "Showing data from 20 of N assistants."
- When no events match, the list shows "No events match the current filters." When you have no events yet, it shows "No activity events across any assistants yet."
- To see the full activity log for a single assistant, open its detail view and select the Activity log tab.
Activity rows​
Each event appears as a row. Activity rows are read-only. The following information appears on each row:

| Element | Description |
|---|---|
| [1] Status icon | An icon showing the assistant's current status. |
| [2] Assistant name | The assistant the event belongs to. |
| [3] Event type | A colored badge showing what happened. See Event types. |
| [4] Trigger type | A badge showing what caused the event. Does not appear for events without a trigger. See Trigger types. |
| [5] Timestamp | The date and time the event occurred. |
Event types​
AI assistants follow a lifecycle: they start, then alternate between sleeping (idle, waiting for a trigger) and waking (actively processing). Starting and stopping control whether the assistant is available at all. Waking and sleeping happen automatically within a running assistant. A running assistant can also be paused, which queues incoming triggers without processing them until the assistant resumes.
Each event has a type that describes what happened to the assistant:
| Event type | Description |
|---|---|
| Wake Event | The assistant woke up and began processing. |
| Sleep Event | The assistant finished processing and went back to waiting. |
| Start Event | The assistant started. |
| Stop Event | The assistant stopped. |
| Pause Event | The assistant paused. Incoming triggers queue until the assistant resumes. |
| Unpause Event | The assistant resumed and began processing queued triggers. |
| Error Event | The assistant encountered an error during processing. |
| History Compactify | The assistant summarized older conversation history into a rolling summary to free context window space. This corresponds to the Compactification history management tier. |
| Memory Indexed | The assistant indexed its conversation history for the Semantic retrieval history management tier, enabling search by meaning in future wake cycles. |
Trigger types​
Events that result from a trigger show a trigger badge. The following trigger types can appear:
| Trigger type | Description |
|---|---|
| User Message Trigger | A user sent a direct message to the assistant. |
| Forum Post Trigger | A new post or reply appeared in a forum the assistant monitors. |
| Scheduled Task Trigger | A scheduled task fired. |
| Manual Trigger | A user manually triggered the assistant. |
| Custom Event Trigger | A custom event reached the assistant through the API. |
| Assistant Message Trigger | Another assistant sent a message to this assistant. |
| Initial Startup Trigger | The assistant started. |
Download activity​
Click Download to save the listed events as a JSON file named assistant-events.json. The file includes only the events that match your current search and time range.
The file is a JSON array of event objects, with the newest event first. Each object has the following structure:
[
{
"id": "EVENT_ID",
"assistant_id": "ASSISTANT_ID",
"event_type": "EVENT_TYPE",
"trigger_type": "TRIGGER_TYPE",
"trigger_detail": {},
"chat_session_id": null,
"wake_cycle": null,
"created_at": "CREATED_AT_TIMESTAMP",
"assistant_name": "ASSISTANT_NAME",
"assistant_status": "ASSISTANT_STATUS"
}
]
The following table describes each field:
| Field | Description |
|---|---|
id | The unique ID of the event. |
assistant_id | The ID of the assistant the event belongs to. |
event_type | The type of event: wake, sleep, start, stop, pause, unpause, error, compactify, or memory_index. |
trigger_type | The type of trigger that caused the event: user_message, forum_post, scheduled_task, manual, custom_event, assistant_message, or initial. null for events without a trigger. |
trigger_detail | An object of additional data about the event. Contains details such as the trigger source for wake events, error messages for error events, and compaction metrics for history compactify events. Empty ({}) for start, stop, pause, and unpause events. |
chat_session_id | The ID of the chat session associated with the event. null when no chat session is involved. |
wake_cycle | The sequential number of the assistant's wake cycle during which this event occurred. A wake cycle is one run of the assistant from trigger to sleep. null for events outside a wake cycle. |
created_at | The date and time the event was created. |
assistant_name | The name of the assistant. |
assistant_status | The assistant's current status: running, sleeping, stopped, paused, or error. |
Related topics​
- Submit and view feedback for this page
- Send feedback about Enterprise h2oGPTe to cloud-feedback@h2o.ai