PotomAndroid ↗
Conceptual artwork, not an app screenshot.
A link can appear in an app's pending list and still not be a finished saved item. That distinction matters when a short video, article, or post says that analysis is temporarily unavailable. Repeatedly tapping Retry is understandable, but it rarely creates new information.
Use this recovery checklist for saving workflows.
First, identify what you actually have
There are two different states that can look similar at a glance:
- A pending link is a request that has not finished processing. It can have a retry action, but it is not proof of a completed card or searchable record.
- A completed saved item is the record you can open and check. It should preserve the source and whatever information the app says it captured.
Whether a pending link can become complete depends on the app and accessible data. Treat the original address as useful evidence, not as a finished record.
Check what Android actually sent
Android's standard Sharesheet sends a specific kind of data to the receiving app. A browser commonly shares the page URL as text; an image or video is normally shared as a URI, with access permissions that the receiving app needs. Sending a link therefore does not mean the receiving app received the video file, your signed-in session, or every detail visible in the source app. Android's sharing documentation describes these different payloads.
Before retrying, open the source again and check three simple things:
- Is this the expected item link, rather than an unrelated caption, search-result page, or message preview? A short TikTok link can be a valid link by itself.
- Does the source open on this phone while you are using the intended account?
- Did you mean to share a link, a screenshot, or a local file? Those are different inputs and an app can handle them differently.
Look for an account problem before blaming the link
While investigating one Potom support case, we found an expired account session alongside immediate temporary-analysis messages for short-video links. The Retry action in Account → Devices only reread device state; it did not renew the account session. A retry on a pending card is a different action: it can ask for that card to be processed again. The initial reason for the expired session was not established. This one case does not show that every unavailable TikTok or Instagram link is an account problem, a platform restriction, or a source failure.
The useful general rule is narrower: if the app explicitly says that the session expired and offers a sign-in control, sign in there first. A retry button inside a pending list may repeat processing, but it cannot always restore credentials. If the account screen has no sign-in option, the Devices retry cannot renew a session; do not sign out of every device just to force it. Contact support or wait for an available app update, then return to the original pending entry for one deliberate retry.
Preserve the useful part while the result is unfinished
If the link matters, write down why before you leave the screen. For example: “backpack zip repair for the green bag” is more useful later than “interesting video.” Keep the original URL and, where you are allowed to do so, a clear frame or your own short note about the step you needed. Do not copy private material into a new service just to work around a failed request.
This is a fallback record, not a claim that the original content has been archived. A link can later change, disappear, or require an account. A screenshot shows only what was visible. Your note preserves your reason for saving it. Each serves a different purpose.
If your app later completes the item, open it once. Check the source, title, and any extracted details against the original before relying on them. If it does not complete, your note still gives you a concrete way to search for the creator, phrase, technique, or task elsewhere.
Retry once, then collect a useful report
Retry after you have changed something meaningful: you signed in again, opened the source under the right account, selected the intended item, or confirmed the network.
If the problem remains, report only the details that help reproduce it safely: the time, the app version, whether the source opened for you, whether it was a link, image, or file, and the exact visible error category. Do not send passwords, session tokens, private links, or screenshots containing personal data. An error message that distinguishes “session expired” from “source unavailable” is more useful than a guess about why it happened.
The goal is not to make every link process. It is to avoid losing the reason you saved it while you resolve a specific problem. For more guides on keeping and returning to useful finds, visit Potom Guides.
