# Events
The Events screen shows a live stream of [events](https://learn.mechanic.dev/core/events) — the triggers that cause your tasks to run. Use it to monitor your automations, and to investigate when a task isn't behaving as expected.
## Event list
Events are displayed in reverse chronological order, showing the time, topic, and task results for each event. The list updates in real time as new events arrive.
### Filtering
Use the **Filters** button to narrow results by search text, date range, error type, event topic, or specific task. The **Errors** tab provides quick access to all events where something went wrong.
Save filter combinations as **custom views** to quickly return to filtered lists you use often.
## Event detail
Click any event to see exactly what happened: which tasks ran in response, what actions they performed, any errors encountered, and the raw event data (JSON).
If a task failed due to a temporary issue (like a network error), you can **retry** the event to run it again. Use **cancel** to stop a queued event that hasn't started processing yet. You can also **export** the event and all related data as JSON via email — useful for debugging with support or archiving.
---
# 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://learn.mechanic.dev/app/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.
