> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/buildertek-ticketing-guide/error-messages-and-troubleshooting.md).

# Error Messages & Troubleshooting

#### Common Login Errors

* Error: "Invalid credentials"\
  Resolution: Reset your password via the login screen.
* Error: "Session expired"\
  Resolution: Re-login and ensure cookies are enabled in your browser.

#### Ticket Submission Errors

* Error: "Missing required fields"\
  Resolution: Ensure all mandatory fields (marked with \*) are filled.
* Error: "Server timeout"\
  Resolution: Check your internet connection and retry.

#### Email/Notification Issues

* Issue: Email not received after estimate submission\
  Resolution: Check spam folder; ensure BuilderTek domain is whitelisted.

#### How to Report a Bug

If you encounter a technical issue:

1. Create a new case with Type = "Bug"
2. Include error messages and screenshots if possible
3. Submit and await technical team response


---

# 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://docs.buildertek.com/buildertek-ticketing-guide/error-messages-and-troubleshooting.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.