My issues aren’t showing up

How long does the first import take?

The first import usually takes a few minutes: right after you connect, Karrow brings in your 12 most recent published issues in the background.

While it runs, the Publications page shows “Importing back catalog…” on the publication, Settings → API keys shows “importing…” next to its name, and, until the first issues arrive, the issue list in the editor says “Importing back catalogue…”.

Only those 12 come in at first. Karrow needs a handful of recent issues to learn your voice, and issues older than those 12 aren’t imported later.

Why is my new issue missing?

A new issue can take up to 15 minutes to appear, because Karrow checks your newsletter for new issues every 15 minutes.

Many arrive sooner. When you connect, Karrow also asks beehiiv or Ghost to tell it the moment an issue goes out. If your plan or site allows that, the issue shows up within moments; if not, the 15-minute check still picks it up.

Each check looks at your 10 most recent published issues and brings in any Karrow doesn’t have yet, so several issues sent close together all arrive on the same check.

If New-issue alerts is on in Settings → Notifications, you also get an email when a new issue arrives. Alerts only go out for issues published in the last 48 hours, so connecting a publication doesn’t send one for every old issue.

Which issues does Karrow import?

Karrow imports published issues only: drafts and scheduled issues in beehiiv or Ghost appear once they’re sent.

From beehiiv, Karrow reads the email version of each issue, and the premium version when an issue has one. A post with no email content is skipped, because there’s nothing for Karrow to read.

From Ghost, Karrow reads posts with the published status. A post with no body is skipped.

If you edit a beehiiv issue after it was imported, Karrow keeps the version it already has. With Ghost, unpublishing and republishing a post sends it again, and Karrow replaces its copy with the new version.

If you have more than one publication, check you’re looking at the right one. The issue list in the editor shows one publication at a time; switch it with the publication picker at the top of the list.

Is a whole publication missing?

If a whole beehiiv publication is missing, it was probably not selected when you connected the key. One beehiiv key can reach every publication in that beehiiv workspace, and you choose which ones to connect.

To add one, open Settings → API keys, click Add publication on that key, pick the publication, and click Add. Karrow then imports its 12 most recent issues, the same as the first time. If the list says “No more publications available on this key.”, every publication the key can reach is already connected.

A Ghost key connects one site. For a second Ghost site, click Connect publication and enter that site’s address and its own Admin API key.

Why does it say “Connection error, reconnect needed”?

It means beehiiv or Ghost stopped accepting the API key Karrow uses, for example because the key was deleted or the integration was removed, so no new issues come in until you replace it.

Settings → API keys shows the same problem as a Reconnect needed badge on that key. One beehiiv key can cover several publications, so every publication under it shows the error at once, and one new key fixes them all.

1. 1Create a new key in beehiiv (Settings → Workspace → API) or Ghost (Settings → Integrations → Add custom integration, then copy the Admin API key).
2. 2In Karrow, open Settings → API keys, find the key marked Reconnect needed, and click Update key.
3. 3Paste the new key and click Save key. The badge changes back to Active.

Use Update key, not Disconnect. Disconnect removes the publications under that key and all their imported issues.

What happens after I update the key?

Karrow picks up on its next check, within 15 minutes: it looks at your 10 most recent issues and brings in any that went out while the key was rejected.

If more than 10 issues went out while the key wasn’t working, the older ones won’t come in. For example, if you publish daily and the key was broken for two weeks, 14 issues went out: the next check brings in the newest 10, and the first 4 stay missing.

If Karrow turns the new key down with “Invalid or unauthorized API key”, check you copied the whole key. For Ghost, Update key checks the key against the site address you first connected, so it must be an Admin API key from that same site.

If you see “That source is rate-limiting us right now. Try again shortly.”, beehiiv or Ghost is limiting requests for a moment. Wait a minute and save the key again.

What if it keeps saying importing?

Occasionally the first import stops partway and the status stays on importing. New issues still come in on the regular check, so nothing is lost going forward.

If it’s still importing after a while, contact us from the support page with the publication’s name and we’ll take a look.