Why chats need a connection, what still works without one, and why nothing is queued to send later
Anything that moves a job forward needs a connection: the assistant has to reach the AI service, and every step has to be confirmed by your organization's systems. So Streamliner does not pretend. Without a connection, a message is not sent, and you know at once.
What you see
- Not delivered · Try again under your message. Tap it when you are back online to send it again.
- Offline — messages can't be sent.
Nothing is saved up to send later. A step made later, without you watching, could act on a price or a stock level that has since changed, so you decide when to try again.
What still works offline
- Opening the app and reading every chat on the device, with its cards.
- Copying a chat reference or anything a card offers to copy.
- Settings.
- The Meridian demo, completely: its systems and assistant run on your device.
What doesn't
- Sending messages and tapping buttons that act, in an organization or on this device.
- Confirmation cards, secure forms and sign-in cards, which all talk to your organization's systems.
- Fetching a new setup from your organization, and the Usage page.
Patchy connections
If a reply stops partway, the chat says so, for example The answer was cut off before a step was complete. Look at the activity lines and the overview to see what your organization's system actually did before you ask again. A step is done only when the system confirms it.
The same manual ships inside the app. This section as Markdown