Contents
The Events Page
Event List Actions
Discovered vs Configured Events
Finding Your Event
Live Status at a Glance
Configuring an Event
When an Event Completes
The Events Page
Open Events in the left nav. Across the top are four filters: a Season dropdown, a Program dropdown (All / FRC / FTC), a Hide past events checkbox, and a Show unconfigured checkbox (it shows a count in parentheses). The table below lists: Code, Event Name, Dates, Stream Key, Phase, Status, Clips, and an Actions column.
The Season List Includes Next Year
The season filter always offers the upcoming season in addition to the current and two prior ones, since some events are scheduled and published before the calendar rolls over. It doesn’t switch itself — you (or your Client Admin) pick the season you need.
Event List Actions
The Actions column shows only the buttons that apply to each row’s status. Buttons you can’t use are dimmed, with the reason on hover or tap.
- Configure — on discovered events. Needs Client Admin.
- ▶ Preview — on 🔴 LIVE and Pre-event test rows. Any member can use it, Readonly included, unless system administrators have turned previews off.
- Complete — on 🔴 LIVE and In Progress rows. Confirms first: “Mark “event name” as completed?” / “The event moves to Completed.” Needs User or above.
- Reopen — only on COMPLETED rows. Confirms first: “Reopen “event name” as In Progress?” / “The event returns to In Progress.” Needs Client Admin. See When an Event Completes.
- Edit — on scheduled and in-progress rows; opens the event’s configuration page (see Configuring an Event).
- Unconfigure — on scheduled rows. Confirms first: “Unconfigure “event name”?” / “The event will return to Discovered status.” Needs Client Admin.
- Enable Signage / Disable Signage — on configured events whose stream key has signs. Disabling confirms first: “Signs on this stream key will return to the idle page.” Needs User or above. See Signage for when it can be turned on.
Discovered vs Configured Events
The platform automatically discovers upcoming events from the FIRST Events APIs, so a new event usually already exists on the Events page before anyone touches it. A discovered event only has a name and needs a stream key added before it can do anything — the Events page shows it dimmed and greyed-out (not clickable) with a blue Configure button instead of a link, and discovered events are hidden by default behind the Show unconfigured checkbox. An event becomes configured once a Client Admin fills in the rest of its setup — after that its row lights up, becomes clickable, and shows a normal status badge.
Everyone sees the Configure button; below Client Admin it is dimmed with ”🔒 Needs Client Admin”. It can also be refused for the event itself, with “Event has no dates from FIRST API” or “Outside your client’s district or states”.
Off-Season and Some Out-of-Territory Events May Not Appear
If an event you expect to see is missing, it may not be visible to your organization yet — see
Troubleshooting.
Finding Your Event
Filter by program and season to narrow the list down, and turn on Hide past events (on by default) to see what’s coming up. It hides a configured event once its stream window has ended, and a discovered event once its last day has passed in its own timezone; live, pre-event-test and test events always show. Status badges you’ll see in the Status column: SCHEDULED, Pre-event test, 🔴 LIVE, In Progress, COMPLETED, and ERROR. A live event also shows a running elapsed-time counter next to its status badge, and, if it’s restreaming, a ▶ YT Live badge next to its name. Clicking a live event’s status cell (instead of its name) opens a metrics popup instead of navigating into the event.
The purple Pre-event test badge shows when video arrives before the event’s start time (up to a day early). It switches to 🔴 LIVE by itself at the start time, without reconnecting OBS. Start Push is refused until then, unless the event has a setup-day test video (see The Setup-Day Test Video). The elapsed counter, the metrics popup and ▶ Preview work for a pre-event test the same as for a live event.
Live Status at a Glance
Opening a configured event takes you to its control center — see Running a Live Event for what’s there. Any member, Readonly included, can click ▶ Preview on a live or pre-event-test row to watch the stream without opening the full control center, unless system administrators have turned previews off.
Configuring an Event
Configuring a newly-discovered event (clicking Configure) is a Client Admin action — if you’re not a Client Admin yourself, ask one to do this before the event needs to go live. Afterwards, Edit on the Events list (or the settings link in the control center, which reads Edit, or View settings if you can’t change the basics) opens the configuration page. Every member can open it; the tabs are Basics, Livestream, Blue Alliance and Signage:
- Basics — event name, timezone, the stream key it will receive video on, which YouTube channel clips upload to, and an optional pre-roll video. The timezone is set by system admins only.
- Stream window (on the Basics tab) — “When the stream key may publish, in the event’s time zone (timezone). A publish is also accepted from a day before the start as a pre-event test.” Editing it needs Client Admin. Stream window times show in the event’s timezone, with the zone’s abbreviation (for example “Mar 26, 4:30 PM EDT”), in the control center header as well; see When FIRST Reschedules an Event.
- Livestream — whether and how this event restreams to a full YouTube broadcast (see Running a Live Event), which channel it broadcasts to, and a thumbnail.
- Broadcast days (on the Livestream tab, when the event restreams to YouTube) — the YouTube broadcast for each day of the event. See YouTube Broadcasts.
- Blue Alliance (FRC events only) — credentials needed so match results and video links get posted back to The Blue Alliance.
- Signage — which event signs (if any) should show this event’s stream or queue information (see Clips, Uploads and Signage).
A 🔒 next to a field label means that field is locked, and a section you can’t edit shows one ”🔒 reason” line under its title. Some fields lock because of the event’s state rather than your role — for example, the restream mode and channel can’t change while broadcasts are open. See Field Locks.
For the exact meaning, allowed values, and defaults of every field on this page, see Event Configuration Reference.
When FIRST Reschedules an Event
If FIRST moves an event’s dates after its stream window was set by hand, the platform normally
replaces that window with one based on the new dates. It keeps the hand-set window instead if the
event is live, in a pre-event test or completed, or if the new window would overlap another event.
Either way, the Stream window section shows a notice until someone deals with it:
- “FIRST changed this event’s dates (date). The hand-set stream window was replaced with FIRST’s
new dates. Check it and save.” - “FIRST changed this event’s dates (date). The hand-set stream window was kept. Check it against
the new dates.”
Check the window against the new dates, then click Save, or Use FIRST’s dates to reset it;
either clears the notice. A Client Admin does this, since editing the window needs Client Admin.
When an Event Completes
An event moves to COMPLETED in one of two ways:
- Someone clicks Complete on its row (User or above).
- It completes itself. An In Progress event whose stream window ended more than a grace period
ago (120 minutes by default), with nothing recording, is marked completed automatically. A live
feed is never cut, and test events are never completed this way. System administrators can turn
this off or change the grace period (Event Auto-Complete in
System Settings).
There is no separate step to clear a stuck live session: an event that still reads 🔴 LIVE after
your stream has stopped heals itself within about 2 minutes.
A completed event refuses new OBS publishes. If you need to stream to it again, a Client Admin
clicks Reopen to return it to In Progress. Reopen is only offered on completed events; on
anything else it’s refused with “Only a completed event can be reopened”, or “Nothing to reopen —
the event hasn’t started” before the event has started.