> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-activity-timeline.md).
# Incident Activity Timeline
You can access the **Incident Activity Timeline** for a particular incident on the **Incidents** page in the web app and the timeline will be displayed on the right-hand side of the **Incident Details** page.
The Incident Timeline will display the timeline of the incident in reverse chronological order for the following details:
**(a)** when the incident was first **Triggered** and **Acknowledged**
**(b)** who **Acknowledged** it
**(c)** who **Reassigned** it and who it is **Reassigned** to
**(d)** who **Resolved** it and when
**(e)** what message was posted on the **Status Page**
**(f)** by whom and when the **Postmortem** was created
**(g)** what **Action** was taken
**(h)** starred comments from the **Notes**
**(i)** if the incident is suppressed due to a **scheduled maintenance**
**(j)** if the incident is routed due to a **Routing Rule**
**(k)** if the incident is suppressed due to a **Suppression Rule**
#### Exporting Incident Activity Timeline
The automated **Incident Activity Timeline** serves as a real-time chain of incident resolution activity. You can download this and use it for **Incident Reviews** or create **Postmortems**. **Incident Activity Timeline** can be exported by clicking on the **Download** icon at the top right corner of the **Activity Timeline**. You can download this in PDF or CSV formats.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-activity-timeline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.