Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: StoresFlow

When the network drops

What StoresFlow's pages show when the device loses its connection, what this browser tab keeps, how to check an unconfirmed recording when it returns, and what a Supervisor sees.

Review edition · 18 November 2026 · For Operator, Supervisor, Owner, Author, Reviewer

On this page

This page is about the device you work on losing its connection to StoresFlow: a handheld at a working station, or a computer in the office. StoresFlow has no offline mode. Nothing is recorded until the device reaches StoresFlow again, and nothing is sent again by itself when the connection returns. For an unconfirmed recording on its own, read recover an unconfirmed recording.

What the pages show

What you see depends on what you pressed:

  • A search, a filter or a link, such as Search stock, Search stations or a link between pages, says under the button or link you used: "The connection was lost. No answer came back from StoresFlow, and nothing was changed. Try again when the connection is back." Nothing was recorded. Press it again once the connection is back.
  • Choosing a working station, Finish this station session, and enrolling a working station on Team and stations, say under the button: "The connection was lost. No answer came back from StoresFlow, 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 StoresFlow for the page again and sends nothing you pressed. While the connection is still down it says "The connection is still lost."; once StoresFlow answers, "The connection is back. This page now shows what StoresFlow has recorded: check whether what you sent is there before you try again." Where StoresFlow did receive the press, the reloaded page can also show StoresFlow's own answer at the top, such as "Station selected.". Where the reloaded page pushed "The connection is back." out of sight, the page moves to show it, unless StoresFlow's answer at the top leaves no room for both. Choosing the station or finishing the session again is safe.
  • A scan into Scan the material says "The lookup could not be completed. No movement was recorded."
  • Check this movement says "The checks could not be completed. No stock was changed." On Transfers, checking an arrival says "The arrival checks could not be completed. Nothing was recorded."
  • A button that checks and records in one press, such as Pick and issue on Requests, an adjustment, or a count observation, says "The checks could not be prepared: no answer came back from StoresFlow. No stock recording request was sent, so nothing was recorded. Try again once the connection is back." when the checks got no answer. Press it again once the connection is back. Prepare this reviewed acceptance on Reviewed imports says the same of an import: "No acceptance request was sent, so nothing was accepted." Once StoresFlow is preparing or accepting an import in the background, the page asks how it is going every second or two, and a question that gets no answer is simply asked again.
  • Record this movement, and every other button that records (a demand, a reservation, a hold, a count, an adjustment, Pick and issue), shows "We have not confirmed the result." with the original request ID and Check the original request, when its own answer got lost. The recording may or may not have reached StoresFlow. This never shows the connection message as well.
  • A step on Pick orders says "The answer was lost. Check this same step again; it is never recorded twice." with Check again. Picking a ticket's lines moves no stock. Where stock comes off at the pick or moves to despatch staging, finishing the pick does, and Check again finds that finish recorded once, with its stock taken once.
  • Print here for a pick ticket says "The answer was lost. Check this same request again; it will not print a second copy."
  • After a recording StoresFlow made, the page asks StoresFlow for its updated records. If that gets no answer, it says "The connection was lost. This was recorded, but no answer came back from StoresFlow before this page could show it. Reload this page to see it before you go on." with Reload this page. Do not record it again: it is recorded. Once StoresFlow answers, "The connection is back. This page now shows what StoresFlow has recorded."

StoresFlow does not say that the device is offline before you press something. A page that is already open stays as it was.

While a recording is unconfirmed

Until the original request is checked, the page keeps it. Its recording buttons cannot be used, StoresFlow's own links and menu do not open, and the browser asks you to confirm before you leave the page. Note the request ID the message shows, and keep the page open.

What is kept, and for how long

  • An unconfirmed movement, with what you entered, is kept in this browser tab for you and this site. Reloading the tab keeps it, and the page offers Check the original request again. Signing in again in the same tab as yourself, after the station locks, keeps it too. Closing the tab, signing in in another tab or changing to another site loses it from the tab.
  • A material or policy draft, and a site's closure and review steps, are kept only while the page is open. A reload loses them from the tab.
  • A step on Pick orders is kept only while the page is open.
  • Print here keeps the request in this tab until PrintStation's answer is read, so checking it again never prints a second copy.
  • The checks made by Check this movement last 2 minutes. A recording sent after that is refused.
  • StoresFlow's own answer to every request it recorded is kept, so Check the original request finds it however long the connection was gone.
  • The working station stays yours for 10 minutes without activity. After that it locks, and a page opened then says "Station locked".

When the connection returns

Choose Check the original request before you reload the page or do anything else. It asks StoresFlow about the same request, under its original ID, and never starts a new one:

  • Recorded.: StoresFlow has it. Nothing more is needed. If the page then says the connection was lost, choose Reload this page to see it.
  • "The authorised lookup found no record of this original request." with Retry the original recording: nothing was recorded. The retry sends the same request again, under the same ID, never a second one. It records the movement you already made: do not move the material again.
  • Not recorded: with a reason: deal with that reason. Where the checks are more than 2 minutes old, or the station locked meanwhile, the retry says "Not recorded: these checks changed or expired. Check the same physical choice again. Do not repeat a movement that has already happened." Check the same movement again and record it, without moving the material again.

If StoresFlow still cannot be reached, the message stays. Check again in a moment.

If the station locked meanwhile

If the connection was gone for more than 10 minutes, the station has locked. Check the original request still works on the page that shows it, so check first.

If you reloaded the page, it now says "Station locked" and "One action is still unconfirmed: request ID" with the request's ID, then "This tab keeps it for whoever started it. Sign in again here as that person, then check it with its request ID before doing it again." Choose Sign in again in the same tab, as yourself, and choose the station: the recording comes back as not yet confirmed, with Check the original request. Check it before anything else. Sign in again goes to SmartFACT Accounts even while the recording waits, and the browser does not ask you to confirm leaving the page.

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 in a browser that has worked at a working 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 the 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.

Someone else signing in at that tab is never offered your recording. Closing the tab, or signing in in another tab, loses it from the tab: note the request ID first. A step on Pick orders is not kept: the lock says "This tab cannot keep it once you sign in again. Note its request ID now, and check whether it was recorded before doing it again."

Where the recording is lost from the tab, choose the station after signing in and look for the movement before recording it again: open Retained history, then Stock movements, and find it by its material, time and your name. Record it only if it is not there.

What the Supervisor sees

StoresFlow does not show anyone that a device has lost its connection. A movement appears in Retained history only once it has been recorded, with who recorded it and when, and its Command receipt shows the request ID. A movement whose recording never reached StoresFlow is not there, and the stock shown for those bins differs from the shelf until someone records it. Where an operator reports an unconfirmed recording that can no longer be checked, compare the bins with Retained history and record what is missing, or count the bins. Adjusting stock with a reason is in corrections and holds.