The assistant now tells us why it could not save a conversation

The Sustentus assistant keeps answering even when the system it saves conversations to is briefly unavailable. A short interruption costs you your history, never your assistant — you still get your answer, and since August the Sustentus team has been able to see when that happened.

There was a gap in what it could see. Some conversations are not saved because something broke, and some are not saved because the store deliberately declined to write them — and only the first kind was ever recorded. The second kind produced no trace at all: the assistant answered normally, the conversation quietly went unsaved, and nothing anywhere said so.

Both kinds are now written down, and each one says which it was. The team can tell at a glance whether something is failing or whether the assistant is being turned away, which are two different problems with two different fixes. The most common cause of the second — a change that has been released but not yet fully applied — is now visible while it is happening rather than afterwards.

Recording it also costs less than it did. A conversation that runs into several problems at once is now written down in one go rather than one entry at a time, which matters most during exactly the kind of interruption these records exist to capture.

Nothing changes in how you use the assistant, and nothing about your conversations is shared outside Sustentus. Records are kept for 30 days.