# When the network drops

What the floor station, the stores board and the office pages show when the device loses its connection, what is kept, how to check an unconfirmed action when it returns, and what a Supervisor sees.

Source: https://help.smartfact.ai/manuals/refillflow/when-the-network-drops

Review edition: 13 November 2026

Roles: operator, stores, supervisor, owner, author, reviewer

This page is about the device you work on losing its connection to RefillFlow: the floor station, the stores board, or a computer in the office. RefillFlow has no offline mode. Nothing is recorded until the device reaches RefillFlow again, nothing is kept on the device for later, and nothing is sent again by itself when the connection returns. For an unconfirmed action on its own, read [uncertain results](/manuals/refillflow/uncertain-results).

## What the pages show

What you see depends on where you are:

- **At the floor station**, the status line says "Offline: nothing is recorded" as soon as the device knows it has lost the connection, or when the station's regular check with RefillFlow gets no answer, and scanning stops: "Capture paused: offline, nothing is recorded." A scan made then is neither sent nor kept. When the connection returns the status line says "Connected" again and scanning resumes: scan the card again.
- **Start working here** says "Not started: the connection was lost. Nothing is assumed; try again."
- **Request refill**, **Record received** and the other buttons that record at the station say, when their answer got lost, "Unconfirmed: RefillFlow has not answered about" the action, "It may or may not be recorded", with **Check the outcome**. While the station is offline that button cannot be pressed: "Offline: check the outcome when the connection is back."
- **On the stores board**, Accept, a pick, Dispatch, a shortage and the other actions on a refill say "Unconfirmed: RefillFlow did not answer about" the action, "It may or may not be recorded. Check the outcome before anything else on this refill.", with **Check the outcome** on that refill.
- **On the office pages**, a button that sends something, such as **Create the site**, **Open the sample site**, a reference data form (items, locations, stores queues, loops and containers), **Team & stations**, the calendar, a CSV import, an export, retrying a document on **Tickets and cards** or **Use this browser as the sample station**, says under the button: "The connection was lost. No answer came back from RefillFlow, so it is not known whether this was saved. Reload this page to check before you try again." with **Reload this page**. That reload asks RefillFlow for the page again and sends nothing you pressed. While the connection is still down it says "The connection is still lost."; once RefillFlow answers, "The connection is back. This page now shows what RefillFlow has recorded: check whether what you sent is there before you try again.", with RefillFlow's own message at the top of the page where your press reached it, such as the location created or why it was refused. If the reloaded page pushed "The connection is back." out of sight, it is brought back into view. Pairing a browser as a station is the one exception: the station's cookie comes back only in RefillFlow's answer, so where that answer was lost no message says this browser is the station. **Team & stations** then lists the station as paired, but this browser is not it: pair it again, which replaces the earlier secret.
- **After a press RefillFlow recorded**, such as **Accept** on the stores board, **Request refill** at the station or **Send** on **Tickets and cards**, the page then asks RefillFlow for its updated records. If that gets no answer, it says "The connection was lost. This was recorded, but no answer came back from RefillFlow before this page could show it. Reload this page to see it before you go on." with **Reload this page**. Do not press the button again: it is recorded. Once RefillFlow answers, "The connection is back. This page now shows what RefillFlow has recorded."
- **A filter** on **History** or **Reports** says "The connection was lost. No answer came back from RefillFlow, and nothing was changed. Try again when the connection is back."

A form that adds something, such as **New location**, keeps what you typed until RefillFlow answers that it was saved, and empties then. After **Reload this page**, look for it in the list, and press the button again only if it is not there. Adding the same code twice is refused.

## What is kept, and for how long

- **Nothing is kept on the device for later.** A scan made while the station is offline is gone.
- **An unconfirmed action** is kept in the page's memory, at the station and on the board, until you check it. Reloading or closing the page loses it.
- **Your session at the station** is held in the tab's memory for 3 minutes at a time, and renewed while the page can reach RefillFlow. If the connection is gone for longer, the session lapses, and when the connection returns the station says "Your session at this station ended: your session at this station lapsed. Start again." An unconfirmed action is not lost with it: see below.
- **A prepared request**, scanned and checked and waiting for your confirmation, lasts 2 minutes. An urgent request waiting for a Supervisor's approval lasts 12 hours.
- **After 15 minutes without activity** the station locks, and the next person signs in again. While an action is unconfirmed, the lock waits until you have checked its outcome.
- **RefillFlow's own record** of every action it recorded is kept, so **Check the outcome** is answered from it however long the connection was gone, even after your station session has lapsed. It answers only you, at this site.

## When the connection returns

Choose **Check the outcome** before anything else. It sends the same action again, under its original identity, and RefillFlow records it at most once:

- The action's usual answer, such as "Request recorded for" the container: it is recorded, once.
- **Not done:** with a reason: deal with that reason.

If RefillFlow still cannot be reached, the action stays unconfirmed. Check again in a moment.

## If your station session lapsed meanwhile

If the connection was gone for more than about 3 minutes, your session at the station has lapsed. When the connection returns, the station says "Your session at this station has ended." and that the action "is still unconfirmed: check its outcome before anything else." The unconfirmed action stays on the page, and **Start working here** is not offered until you have checked it.

Choose **Check the outcome**. RefillFlow records nothing more under the ended session, but it still answers whether the action was recorded:

- The action's usual answer, such as "Request recorded for" the container: it is recorded, once.
- **Not recorded:** "RefillFlow has no record of it, and nothing more is recorded under your ended session." Start working here again and do it again.

If the station also locked meanwhile, it says so and waits for the same check; once the answer is shown, choose **Sign in again**. If **Sign in again** itself gets no answer because the connection was lost, the lock says so under the button: choose **Sign in again** once the connection is back. Whichever way the next sign-in starts at a station, by **Sign in again**, by reloading the page, or by **Sign out** in the menu and then **Sign in with SmartFACT Accounts**, SmartFACT Accounts asks for your own email address and password, so the person signed in before cannot be signed back in by mistake. That is so whether the station had locked or not, and it keeps asking in that browser until someone has signed in. Scanning a container whose request was recorded says "This container already has an open refill. No new request is needed.", so a refill is never requested twice.

The stores board has no station session, so **Check the outcome** on a refill still works after a long outage.

## What the Supervisor sees

RefillFlow does not show anyone that a device has lost its connection. A request appears on the stores board, and an action in a refill's history, only once RefillFlow has recorded it. A refill that was requested while the station was offline was never sent, so nothing waits for it on the board: the container is still empty on the line until someone requests it.
