# What happens when a page will not let us in

> Some pages want a subscription, some never answer, some are behind a login. What Curate does with each, and why your link is safe either way.

- Canonical: https://www.getcurate.ai/blog/capture/what-happens-when-a-page-will-not-let-us-in/
- Language: en
- Published: 2026-09-11
- Author: Curate
- Tags: capture, reliability

---

Not every page can be read. A saving tool that pretends otherwise just loses things quietly, so this is what actually happens in each case.

## The rule underneath all of it

**A capture that fails still saves the item.** Whatever went wrong with reading the page, the thing you sent is in your library, with the URL you sent it from. You can open it, you can retry it, and you can find it later. Nothing is discarded because a fetch did not go well.

That is worth stating plainly because the alternative is common: an error toast, and nothing in the list afterwards.

## The page asks for a subscription

This is the most common one, and it is the one where we say so rather than guessing. Your library shows the item with a note that the page wanted a subscription, and the suggestion that works: open it in the browser where you are already signed in, then share the page to Curate from there. What arrives is the page as you can see it.

## The page never answers

Servers are down, connections drop, rate limits happen. We keep trying in the background for an hour rather than making that your problem, and the item sits in your library the whole time saying what it is waiting for.

## The page is not really a page

A link to a post inside an app that does not serve its content to anyone not logged in is not going to become an article, however many times we try. We say that, rather than leaving something stuck in a retry loop forever, and the item stays saved with whatever we could read.

## You already have this one

Not a failure, but it belongs here. If you save something you have already saved, Curate tells you, tells you when you saved it the first time, and offers to open the one you have. **It does not cost you another of your monthly saves**, because reading the same page twice is our inefficiency, not yours.

## Why none of this is an error dialog

Every one of these states lives on the item in your library, not in a modal you dismiss and forget. The failure is part of the thing's state, so it is there when you come back to it, and it is there with a way forward.

A message box tells you something went wrong once. A row that says *that page wanted a subscription* is still telling you three weeks later, when you finally have time to do something about it.