> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/assessments/safe-exam-browser/seb-error-checklist.md).
# Organization Checklist for SEB errors
Before reporting an exam issue to Shift iQ support, gather the below information:\
Before reporting an exam issue to Shift iQ support, gather the below information:
1. Provide detailed description of the issue that is happening.
2. Confirm if the venue tested the internet connection on the device that is having the issue.\
If the issue is only happening to ONE person in the class, it is an indication that it is a possible venue issue and not a Shift iQ issue. If there was an issue with Shift iQ, it will affect ALL candidates and not just one candidate.
3. Ask for the Venue’s IP Address. The Venue can open and provide their IPv4 address.\
\
4. Confirm the version of SEB that venue is using.\
The current supported versions of SEB: SEB 3.3.2 up to SEB 3.7.0\
This can change, and updates can be found here: \
Venues can see their version installed on the exam login page.\
\
5. Shift iQ records the SEB version used by a user after they login to their exam.\
An administrator can view the SEB versions in the following places:\
i. If using Exam Events, open the event and click on the Grades tab, under the Exam Events Tab. The SEB version will be displayed below the learner's name under the Exam Candidate column.\
ii. In Assessment Attempts, the SEB version will be displayed below the learner's name under the Exam Candidate column.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.shiftiq.com/help/assessments/safe-exam-browser/seb-error-checklist.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.