Alert type 02
The line should be moving.
It isn’t.
Every other camera product waits for something to happen. This one waits for something to stop. Mark a region that is supposed to be active inside a window — a conveyor, a pack station, a dock in its receiving slot — give it a grace period, and livee raises its hand when the work goes quiet. Nobody has to notice the silence.
Setting one up
Three decisions, then it runs.
This is the alert that most often pays for the whole deployment, and it takes about two minutes to define.
- 01
Mark the region
Draw the part of the image that carries the work — the belt, the station, the trailer mouth. Not the whole frame: a person walking past should not count as the line running.
- 02
Set the window
When is this supposed to be active? 14:00–22:00 for the pack line. The booked slot for a dock. Continuous for a cold-store conveyor.
- 03
Set the grace
How long a pause is normal? Three minutes on a pack line, thirty seconds on a high-throughput sorter. Below the grace, nothing happens; above it, the alert fires.
Why it matters
Lost throughput does not report itself.
A stopped line is not an incident anybody files. It is twenty minutes that quietly disappear, several times a week, and shows up only as a number that missed.
The dock that never started
The trailer arrived, the slot opened, and nothing moved for forty minutes because the paperwork was with someone else. The camera saw all of it.
The conveyor that tripped
A jam stops the belt at the far end of the hall. The pack station notices when the work runs out — which is long after the belt stopped.
The station nobody staffed
A window opens with nobody on it. livee does not care why; it reports that the expected activity is missing, and lets a human decide.
Tuning
What keeps a stall alert from crying wolf.
- A grace period matched to the process, not to the clock — a break is normal, ten minutes of nothing is not
- A region tight enough that passing traffic does not read as activity
- A window that matches the shift plan, so a planned stop is not an alert
- An escalation you choose: email the shift lead at the grace, signal the line controller if it continues
- Per-source sensitivity, so a dim cold store and a bright pack hall behave the same way
- A clip of the moment the motion stopped — evidence for the review, not a claim
The alert that fires on nothing happening.
Request a demoFAQ
About stall alerts.
What counts as “activity” in the region?
Movement in the marked region during the window — product on a belt, people working a station, a truck being loaded. You are marking the place the work happens, so the definition is the region you drew rather than a class you picked.
Will a shift break set it off?
Only if you let it. The window and the grace period exist for exactly this: set the window around the shift plan and the grace above the normal pause, and a break is invisible to the rule.
Can it tell me the line restarted?
The alert is raised when the expected motion stops. Whether you want a second notification when it resumes is part of the alert's channel setup, and it is a reasonable thing to ask for on the demo call.