CORE I/O reports connection, license, host, flow, and sign-in problems in overlays, status buttons, widgets, and notifications. Most warnings close automatically after you resolve the cause.
"Lost Connection to API"
The full-screen Lost Connection to API overlay appears after two consecutive server checks fail. CORE I/O first displays Retrying in 5s..., then waits 30 seconds for the next retry and 60 seconds for each subsequent retry. The overlay includes the attempt number and displays Attempting to reconnect... during a check. Click Retry Now to check immediately.
Check the following:
- Make sure the server is running and reachable from your computer. Open the server address that you entered on the connection page in a new browser tab.
- If the server restarted, wait for it to become available. The overlay closes after the next successful request.
- If the address is incorrect, sign out and enter the correct address on the connection page. See Getting Started.
Widget video uses a separate real-time connection. If the overlay closes but a widget remains black, allow a few seconds for the stream to reconnect. Reload the page if the picture does not return.
"All licensed seats are in use"
The license defines the number of simultaneous user sessions. When every seat is occupied, the All licensed seats are in use overlay blocks access. Your session remains valid, and CORE I/O reconnects automatically when a seat becomes available. Click Retry now to check immediately, or click Sign out to release your attempt and return to the sign-in page.
An administrator can view and release occupied seats on the License page.
Health button colors
The Health button in the app bar summarizes the status of all connected hosts:
| Color | Meaning |
|---|---|
| Green | Every host is within limits. |
| Amber (warning) | At least one host reports CPU, RAM, GPU encoder, or GPU decoder utilization of 80% or higher, or a Matrox M264 card reports 75°C or higher. |
| Red (critical) | At least one value reports 90% or higher, an M264 card reports 80°C or higher, a card sensor reports a critical state, or a card fan does not report OK. The button pulses. |
Click Health to view the values for each host. The System tab on the Flows page provides more detailed information.
Errors indicator
The error indicator next to Health turns red when the server reports an error. Click it to view the latest entries. Open All Errors to view the complete log or export it as a PDF. See App Bar and Navigation.
A widget shows a placeholder instead of its flow
- No flow assigned: The widget has not been assigned to a flow. Use the flow picker in the placeholder or the widget menu to assign a compatible flow.
- Parked: The assigned flow is running a profile of another type. For example, a Playout flow may currently use a Record profile. The placeholder identifies the profile that you must activate. Switch profiles on the Flows page or with the Flow Controller. The widget becomes active automatically.
- Flow inactive: The flow exists but is not running. Start it on the Flows page.
A configuration switch was refused
Switching the profile of an active flow restarts that flow. The server can reject the switch, for example while the flow is recording. The selector returns to the current profile and a message explains the reason. Stop the recording or wait for the active task to finish, then try again.
You cannot open an admin page
The Configuration, Permissions, and System pages require the Admin role. If another user opens one of these pages directly, CORE I/O returns to the dashboard. Ask an administrator to change your role on the Users page if you need access.
Sign-in problems
| Message or behavior | Cause and fix |
|---|---|
| Wrong username or password | Local accounts are managed on the Users page. Active Directory accounts use the domain password. |
| Account locked | Too many attempts failed. An administrator can unlock the account on the Users page. |
| Signed in elsewhere | The server allows one session per account by default. Confirm the new sign-in to end the other session. |
| SAML sign-in returns to the login page | The identity provider did not return a valid response. Check the SAML settings under Integrations, or sign in with a local account. |
Timecode or duration looks wrong
Timecode display depends on the recording's frame rate and drop-frame setting. A player and the File Browser can also display slightly different durations for the same range. See Timecode and Frame Rates for details.
When to reload
CORE I/O updates through a live connection, so you normally do not need to reload the page. Reload if a widget remains frozen after the connection overlay closes, or after an administrator changes your role or group membership.