> 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/requests/expiration-and-reopening.md). # Expiration, completion and reopening How request links expire, what recipients see on an expired link, and how to complete, archive and reopen requests. Every request has an expiration date. Expiring stops reminders on requests nobody has responded to. When you're done with a request, you mark it complete or archive it, and you can reopen it later if you need more. ## Expiration New requests expire 30 days after you create them unless you change the **Expires** date on the request page. Templates set this as **Days To Expire** (1 to 365), counted from the day you create each request from the template. A request expires only if it's still **Sent** when the date passes, meaning the recipient hasn't finished. Pipefile checks hourly. When a request expires: * Its status changes to **Expired** and reminders stop. * You get an email saying it expired (or the assigned teammates do). You can turn this email off in your [notification settings](/reminders-and-notifications/notification-settings.md). A request that's already **Responded** doesn't expire. ### What recipients see on an expired link The recipient isn't locked out. When they open an expired request's link, the page tells them it has expired, and Pipefile emails every recipient a fresh link. The fresh link works for 7 days, and uploads made through it are received as normal. {% hint style="info" %} To give a recipient more time without waiting for them to click, reopen the request or edit its **Expires** date. Both stop the expired page from showing. {% endhint %} ### Change the expiration date Open the request, click the **Edit request** (pencil) icon, change **Expires**, then click **Next** and **Save Request**. If the request had expired and the new date is in the future, it reopens without emailing the recipient. ## Mark a request complete When you have everything you need, click **Mark completed** on the request page, then **Mark Complete** to confirm. * The recipient gets a "Request Complete" email saying you've accepted their files. * The link shows the request as complete, and the recipient can no longer upload or make changes. * Reminders stop, and the request moves to **Completed**. * If you've connected cloud storage, you can pick a folder in the same dialog to export the request's files when you complete it. See [Cloud storage integrations and auto-export](/reviewing-and-exporting/cloud-storage-and-auto-export.md). You can mark a request complete from **Sent**, **Responded** or **Expired**. ## Archive a request Click the **Archive request** icon in the request toolbar, then **Archive Request**. Archiving disables the upload link and moves the request to **Archived**. Unlike completing, it doesn't email the recipient. Use it to close requests you no longer need without notifying anyone. You can archive several at once from the dashboard. See [Track and organize requests](/requests/track-and-organize-requests.md). ## Reopen a request You can reopen an **Expired**, **Completed** or **Archived** request. * **Expired:** click **Reopen request** on the request page. * **Completed or archived:** click **More options** (**⋯**) > **Reopen request**. Confirm with **Reopen Request**. Pipefile then: * Re-enables the upload link. * Sets the expiration date to 30 days from today, if it had already passed. * Emails the recipients (and texts them, if they have a phone number and your plan includes SMS) to let them know the request is open again. * Sets the status back to **Sent**, or to **Responded** if every checklist item already has a response. Reminders resume on their usual schedule while the request is **Sent**. {% hint style="warning" %} A request in the trash can't be reopened. Restore it first with **More options** > **Restore request**. {% endhint %} ## Summary | Action | Recipient can upload? | Recipient notified? | Reminders | | -------------- | -------------------------------------------- | -------------------------------- | ----------------- | | Expires | Only via the fresh link Pipefile emails them | No, until they open the old link | Stop | | Mark completed | No | Yes, "Request Complete" | Stop | | Archive | No | No | Stop | | Reopen | Yes | Yes | Resume while Sent | ## Related * [Expired or invalid links](/troubleshooting/expired-links.md) * [Reminders and notification sequences](/reminders-and-notifications/reminder-sequences.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/requests/expiration-and-reopening.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.