> 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/expired-links.md).

# Expired or invalid links

Why a request link, verification code or account email link stops working, and how to get a working one.

## Request links (for recipients)

Every request has an expiration date, set when you create it. If the recipient still hasn't responded by then, the request becomes **Expired** and automatic reminders stop. A request the recipient has already responded to doesn't expire.

When a recipient opens an expired request, they see **This Link Has Expired** and Pipefile emails every recipient a new link. The new link lets them open the request and upload for 7 days.

{% hint style="info" %}
Tell recipients who hit this page to check their email for the new link. It comes from your name at `noreply@pipefile.com`. If it doesn't arrive, see [Emails not arriving](/troubleshooting/emails-not-arriving.md).
{% endhint %}

To give recipients more time and restart reminders, open the request and click **Reopen request**. If the expiration date has passed, it moves to 30 days from today. See [Expiration, completion and reopening](/requests/expiration-and-reopening.md).

A request link also stops opening the request when:

| Situation                                         | What to do                                                                          |
| ------------------------------------------------- | ----------------------------------------------------------------------------------- |
| The request is archived or in the trash           | Restore or reopen it, or send a new request.                                        |
| The request is completed                          | The recipient sees the finished state but can't upload. Reopen it if you need more. |
| The sender's Pipefile account is no longer active | Contact the team that sent the request.                                             |

## Verification codes on forms

Before filling or signing a form, a recipient may be asked to confirm their identity with a code sent by email or text. Each code works for 10 minutes and allows a few tries. If it has expired, use **Resend** to get a new one. See [Fill and sign a form](/for-your-clients/fill-and-sign-a-form.md).

## Links in account emails

| Link                                 | Works for      | If it has expired                                                                                                                                |
| ------------------------------------ | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| New device verification              | 12 hours       | The page shows **This code has expired**. Log in again to get a new email.                                                                       |
| Team invitation                      | 30 days        | Ask a team admin to send the invitation again from the **Invitations** tab. Resending extends it.                                                |
| Password reset                       | A limited time | The page shows **This password reset link is expired**. Request a new one at [pipefile.com/password/reset](https://pipefile.com/password/reset). |
| Email confirmation for a new account | A limited time | Log in with your email and password; Pipefile sends a new confirmation email.                                                                    |

If you have several of these emails, use the newest one.

## Related

* [Login issues](/troubleshooting/login-issues.md)
* [Recipient FAQ](/for-your-clients/recipient-faq.md)


---

# 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/expired-links.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.