A series shows as “Coming Soon” forever

If a volume has been showing Coming Soon for hours or days when you scan it, something’s stuck. Here’s how to diagnose.

Quick recap

Coming Soon means a volume has been approved for our catalog but not yet published to the live data. Normally this lasts a few minutes — see What “Coming Soon” means.

If it’s persisting, one of these is happening:

The catalog publish hasn’t happened yet (rare to be stuck this long).
Your local catalog sync isn’t getting the latest data.
The volume genuinely isn’t published in the latest version of the catalog.

Step 1 — Check My Requests

If you submitted the request:

Open Settings.
Tap My Requests.
Find the volume’s request.

What’s its status?

Pending — Not yet approved. Coming Soon shouldn’t show; you’d see Pending. If you see Coming Soon, that’s odd — try Step 2.
Approved — Approved but not yet published.
Published — Should be in the catalog. Coming Soon shouldn’t show; force a sync.

Step 2 — Force a catalog sync

Open Settings.
Tap Catalog Version to force a sync.
Try scanning again.

If a publish has happened recently, sync should pull it down and the volume becomes Found.

Step 3 — Verify the latest catalog

After syncing, check Settings → Catalog Version to see your version number. If you can compare against our published current version (released notes or app version page), they should match.

If your local version is older, the sync didn’t fully complete. Try again.

Step 4 — Wait if pending publish

If the request is Approved but not yet Published, our team may be batching publishes. Most batches publish within minutes to hours. In rare cases, a batch may take longer.

Wait an hour or so, then try again.

Step 5 — Contact support if stuck > 1 day

If a volume has been Coming Soon for over 24 hours after approval, please contact support with:

The ISBN.
The request ID (from My Requests).
Approximate time of approval.

We’ll look into our publish queue and get it unstuck.

Why does this happen?

Possible reasons:

Backlog in our publishing pipeline. Heavy approval days can create a queue.
Specific batch failure. Rare, but a batch publish can sometimes hit an error and need to be re-run.
Local app cache. Even after publish, your app needs to sync — and sometimes sync state gets confused.

Workaround: add manually

If you really need the volume tracked right now and it’s been Coming Soon for too long:

Use manual entry — Library entry with custom title and metadata.
When the volume eventually publishes, you can replace the manual entry with the proper catalog one (or just keep the manual entry, your call).

Tip

For a smooth experience, scan after a few hours of catalog activity rather than immediately on submission. Our publish cadence catches up after small delays automatically.