When a Companion App Stops Remembering

An app that remembered you last month can stop, and it usually stops without saying so. The causes are mundane: a release changed the behaviour, a limit was reached, a sign-in went to a different account, a reinstall started clean, or a support action reset something. None of these announce themselves, so the experience is simply that continuity is gone and there is no error message to look up.

This is the short companion to what memory means when a companion app claims it, which covers what the feature is and how to test for it. This one covers the ways it goes away.

The five ordinary causes

A limit you were never shown. Retained material is usually capped, and the cap is rarely published. When it fills, something has to go, and what goes is chosen by the app rather than by you. The visible symptom is oldest-first forgetting while recent conversations stay sharp.

A release changed the behaviour. Memory is a feature like any other, and features get rebuilt. An update can change what is kept, for how long, and how it is condensed, and the previous state does not always survive that migration intact. This sits inside the broader pattern in what an app update can change without asking.

You signed in as a different account than you think. Where an app supports both a platform sign-in and an email login, it is entirely possible to create a second account by using the other route, and a second account is a blank one. This is a common cause of sudden, total-seeming loss, and it is recoverable once identified. See what sign-in with Google or Apple links together.

A device change did not carry it. If retained material lives on the phone rather than on a server, moving phones, reinstalling, or restoring selectively can leave it behind. What changes when you switch phones covers the general case.

A reset that was wider than you meant. Clearing a cache, clearing history, and clearing memory are three separate buttons on some apps and one button on others.

What this means for relying on it

The useful conclusion is narrow and worth stating plainly: continuity in these apps is a convenience feature, not a durable store. It is offered without guarantees, its limits are undocumented, and there is normally no restore path when it lapses. An app is not malfunctioning when it forgets.

So if something said in one of these conversations matters to you outside the app, the only dependable way to keep it is to keep it yourself, somewhere you control. Whether an export exists at all, and what it contains, is worth establishing while the account is healthy rather than after something has gone wrong.

Three things to check in the first week

Whether there is any way to see or export what has been retained. If there is not, you have your answer about how much weight the feature can carry.

Whether the app documents its limits anywhere. Most do not. One that does is telling you something about how it expects to be used.

Whether support can restore anything. Asking before you need it costs one message and saves an unpleasant discovery later.

Where this stops

There is no way from outside to distinguish a limit from a defect, or a deliberate change from an accident, and the app will not separate them for you either. That ambiguity is permanent, which is why this is a list of causes rather than a diagnostic procedure — you can usually narrow a lapse to two or three possibilities and almost never to one.

The expectation is the part worth carrying away, not the troubleshooting. Continuity here behaves like a conversation someone else may reset at any time, for reasons that will not be explained, and planning around that is more productive than trying to defend it.