Processing States and Troubleshooting Failed Saves

Troubleshooting

Processing States and Troubleshooting Failed Saves

A save can succeed at keeping the source while still getting only partial extraction. This guide separates capture, extraction, AI processing, and indexing problems so you know what action is actually useful.

What the main states mean

Processing…Sendlore accepted the source and background processing is still running.
Waiting for creditsThe source is kept as a Light save. Richer processing can resume when credits are available.
Metadata-only / partialSendlore preserved available details but could not obtain enough source content for a full extraction.
Needs attentionThe capture ended without a usable note. The Home/Library surface shows a reason and next actions.

Pending saves are checked periodically in the app, so you do not need to repeatedly resubmit the same URL while it is still processing.

When a save says it needs attention

The app can show Retry, an action to open the original source, and a remove control. The reason matters:

  • Not found: the page may have been deleted or the URL is wrong.
  • Login required / access denied: the server could not access the page.
  • Rate limited / bot wall: the source rejected automated access.
  • Script-only: the page loads useful content only after browser JavaScript runs.
  • Unreachable: timeout, network failure, redirect loop, or oversized response.
  • Unsafe URL: Sendlore intentionally refused the destination.

Blocked, private, or login-gated pages

A plain URL save depends on what Sendlore can fetch from the source. Some pages intentionally block automated readers or require your browser session.

The current Chrome extension can optionally include visible page text when you explicitly save the current page. If you are using extension version 1.4.0 with Include the page’s text when I save enabled, an explicit current-page save may provide evidence the server could not fetch itself.

This does not work for every page. Chrome-protected pages and pages whose visible content is only a login screen may still have little useful evidence.

Extension troubleshooting

Common file problems

  • File too large: use a smaller file or split the document.
  • Older Office format: save it again as DOCX, PPTX, or XLSX.
  • No text found: a scanned PDF or picture-only document may not contain machine-readable text.
  • Conversion failed: try another supported format or paste the relevant text as a note.
  • Storage permission error: sign out and back in, then retry. If it continues, contact support.

Use Retry extraction when the source is worth another attempt

Open the saved item, choose More actions, then Retry extraction. The app currently labels this action as using 1 credit. Reprocessing is meant for an incomplete extraction; it is not useful for a truly dead URL unless the source has become available again.

Sendlore is designed to preserve user-owned edits such as organization metadata while reprocessing the source.

When to contact support

Contact support when the problem is account-wide, repeatable across normal sources, or clearly infrastructure-related—for example, every file upload fails, the extension accepts a key but every save is rejected, or the app reports that AI/storage is not configured.

Include the source URL when safe, what you expected, what happened, the approximate time, and a screenshot of the error. Do not send passwords or private API/connection keys.

Contact supportEmail [email protected]