> For the complete documentation index, see [llms.txt](https://synap.ac/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://synap.ac/docs/platform/collections/attempts.md).

# Attempts

The Attempts page lets you view historical attempts taken by your students from this collection. This includes attempts from its quiz content, student-generated practice tests and collection mocks where the collection link has been recorded.

{% hint style="info" %}
**Location:** Collections → select a collection → Attempts
{% endhint %}

### What appears on this page

Synap automatically filters the report to:

* **Origin type:** Collection
* **Origin:** the collection you are viewing

You do not need to search for the collection by name. The filter uses the collection's internal ID, so it still works if the collection is renamed or a quiz title is reused elsewhere.

### Finding the attempts you need

Use the available filters to narrow the list:

| Filter                  | What it helps you find                                                  |
| ----------------------- | ----------------------------------------------------------------------- |
| **Quiz or assessment**  | Attempts from a particular quiz or assessment inside the collection.    |
| **User group**          | Attempts from a particular class or student group.                      |
| **Attempt status**      | In-progress, submitted and other supported attempt states.              |
| **Date or time period** | Attempts taken during a particular period.                              |
| **User attributes**     | Attempts from students with particular data configured for your portal. |
| **Sorting**             | The order in which the results appear.                                  |

The filters you see can depend on your portal settings and permissions.

### Generated attempts and mocks

Student-generated tests remain linked to their collection. Mocks are linked to both the collection and the selected mock. This lets you report on collection activity even though each test is generated when the student starts it.

### Exporting results

Use **Export to Comma-Separated Values (CSV)** to download the results for use in a spreadsheet or another reporting tool. The download only includes results that match your current filters, so check the date range and student group first.

{% hint style="info" %}
If no attempts appear, clear the optional filters while leaving the current collection selected. Add the filters back one at a time to find which one is excluding the results.
{% endhint %}

### What this page does not change

Attempts is a reporting page. Filtering or exporting results does not change student access, item availability, generated-attempt settings or mock configuration.


---

# 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://synap.ac/docs/platform/collections/attempts.md?ask=<question>&goal=<endgoal>
```

`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.