The Minutes page shows how many minutes you have used, which projects used them, and every session in the current period — how long it ran and how it ended.
Where: Control Panel › Minutes.
Minutes used in the current billing period (or trial), out of the minutes your plan includes plus any you bought. Add minutes buys more.
The same minutes, split by project, so you can see which project used them.
One row per session: one viewer, from the moment the video started until the session ended. Choose Last hour, Today or All in this period above the list.
| Column | What it shows |
|---|---|
| What happened | Opens the session's timeline in plain words: start, video, and how it ended. |
| When | When the video started. Streaming now means the session is still running. |
| Project | The project (stream configuration) the viewer opened. |
| Build | The app and the version that ran. |
| Duration | How long the video ran. These are the minutes the session used. |
| How it ended | Why the session stopped. Each value links to its explanation below. |
| Where | The viewer's country and device type. |
| How it ended | What happened | Who can change it |
|---|---|---|
| Max session time reached | The session ran as long as the configuration allows | You, in the configuration |
| Inactivity logout | Nobody touched the stream for too long | You, in the configuration |
| Connection dropped | The viewer's connection was lost for more than 30 seconds | The viewer's network |
| App crashed | Your application closed by itself | You, in your application |
| Viewer closed the page | The viewer closed the tab or left the page | Nobody — a normal ending |
| Viewer reloaded the page | The viewer reloaded, which starts a new session | Nobody — a normal ending |
| Not recorded | No reason was saved for this session | — |
Every stream configuration has a Max Session Time: the longest one session may run. When it is reached the stream ends, even if the viewer is using it, and the viewer sees Session lasted for 15m. Session Expired. (with your number).
When a viewer does not touch the stream — mouse, keyboard or touch — for the time you set, a countdown appears. If nobody clicks before it ends, the session closes and the viewer sees You have been disconnected due to inactivity.
The viewer's browser stopped reaching our servers for more than 30 seconds, so the session was closed and its machine given back. This comes from the viewer's network: weak Wi-Fi, a mobile connection, a laptop going to sleep, or a VPN or proxy that drops long connections.
Your application closed by itself while the session was running. The viewer sees App Crashed.
bUseLoggingInShipping = true is set in your Target.cs. Then contact support with the session's date and time.The viewer closed the tab or the browser, or went to another page. This is the normal way a session ends.
The viewer reloaded the page. The old session ends and a new one starts, so you see the next session in the list right after this one.
No reason was saved for this session. Sessions before 2 October 2026 have no reason, because it was not recorded yet. A session that is still running has no reason until it ends.
If a stream stopped and the reason does not match what your viewer saw, contact support with the date, approximate time (with time zone) and the link used, and we will examine that session.
Last updated