> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/troubleshooting.md).

# Troubleshooting

Fixes for sign-in problems, missing emails and expired links.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Login issues</strong></td><td>What each login message means, and how to fix a login that loops, stalls or won't accept your details.</td><td><a href="/troubleshooting/login-issues.md">Login issues</a></td></tr><tr><td><strong>Emails not arriving</strong></td><td>What to check when your recipients don't get request emails, or you don't get emails from Pipefile.</td><td><a href="/troubleshooting/emails-not-arriving.md">Emails not arriving</a></td></tr><tr><td><strong>Expired or invalid links</strong></td><td>Why a request link, verification code or account email link stops working, and how to get a working one.</td><td><a href="/troubleshooting/expired-links.md">Expired or invalid links</a></td></tr></tbody></table>


---

# 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://support.pipefile.com/troubleshooting.md?ask=<question>&goal=<user_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.