The product once called Wowza Streaming Cloud is now Wowza Video. To schedule an existing live stream, open its details page and use Schedules to add a one-time or recurring schedule; then choose the intended time zone and check the source and stream health around the event.
A schedule sets when Wowza should start or stop a stream, but it does not connect your encoder or prove that the event is reaching viewers. Treat the schedule, the source connection and the health checks as separate parts of the job.
Streaming Cloud is now Wowza Video
Wowza’s current product name is Wowza Video. Older guides and screenshots may use the former Streaming Cloud name and show navigation that no longer matches the current account. Use current Wowza Video documentation for present-day steps, rather than trying to reproduce a legacy screen. Wowza’s current live stream details guide describes the current details page and its scheduling and health information.
This distinction matters when you follow an older tutorial: the concepts may still help, but labels and page locations can change. In current guidance, look for the live stream details page, Schedules, and Go live later. If a control is missing or labelled differently in your account, confirm it against Wowza’s current help rather than assuming that an old screenshot is authoritative.
Before you schedule, make sure the live stream itself exists and that you know how its source will connect. That source could be an encoder, camera or another supported input. A schedule does not upload a video, prepare your YouTube event, or resolve an encoder configuration problem. If YouTube is the destination, check that the channel is enabled for live streaming and that your intended YouTube event is ready; this guide to enabling YouTube live streaming in India covers the channel-side prerequisite.
Find the stream to schedule
Open the existing live stream in Wowza Video and go to its details page. The Schedules tab shows schedules configured when the stream was created and is also where you can add schedules later. This means you do not have to create a new stream simply because you need another scheduled session, though you should verify the selected stream is the one whose input and destination you intend to use.
Check the stream’s identity and configuration before adding a time. For a devotional channel, for example, confirm that the stream points to the correct source and YouTube destination before scheduling the morning bhajan slot. A schedule attached to the wrong stream can be perfectly valid as a schedule and still fail to produce the event you meant to run.
If you are sending video from OBS, the encoder’s output settings still matter. Scheduling in Wowza does not tune keyframes or bitrate at the source. Review how OBS keyframes affect stream quality if you need to check those settings, then confirm what Wowza actually receives rather than treating the encoder’s configured values as proof of a healthy ingest.
Create a one-time or recurring schedule
In Schedules on the live stream details page, select the schedule pattern that matches the event. Wowza documents one-time start and stop, a one-time start or stop, and recurring schedules. A one-time schedule suits a special broadcast; a recurring schedule suits a repeated programme where the days and effective period are consistent.
For a recurring schedule, set the days of the week and when the recurrence takes effect and ends. Take care with the end condition: a programme intended to repeat indefinitely should not be given an accidental end date, while a seasonal series should not be left running beyond its planned period. Revisit the saved schedule after creation to make sure the recurrence reflects the actual broadcast calendar.
| Schedule approach | Useful when | Check before saving |
|---|---|---|
| One-time start and stop | A single event has a defined beginning and end | Both times and the schedule time zone are correct |
| One-time start or stop | You need only one boundary scheduled | The unscheduled boundary will be handled deliberately |
| Recurring schedule | The same stream follows a repeated weekly pattern | Selected days and recurrence start and end are right |
| API-managed schedule | Your operation creates or changes schedules programmatically | Your integration handles the schedule’s lifecycle and state |
The Wowza Video REST API reference describes creating, retrieving, updating, enabling, disabling and deleting schedules, as well as checking their state. This can help if you manage many streams or need a controlled automation workflow, but it also means your integration must account for changes and failures. Use the Wowza Video REST API reference for the current supported operations rather than relying on assumptions from an old script.
For a small channel with one weekly stream, the UI is often easier to inspect and correct. API automation makes more sense when schedule changes are part of a wider system and someone can maintain that integration. Either route only sets the requested timing; neither verifies that the source is connected at start time.
Choose the schedule time zone
When setting a one-time start or stop, select the Time zone for the schedule. Do not assume it uses the computer’s clock, the viewer’s location, or the time zone you used when creating the stream. The schedule should be interpreted against the time zone you deliberately select.
For example, if a channel operator in India plans a recurring evening programme, enter the intended local broadcast time and explicitly confirm the chosen zone before saving. If a collaborator is scheduling from another country, share the time zone alongside the calendar time; “start at 7” is ambiguous without it. Check the saved schedule after creation, especially when the event time has been copied from a calendar or a message.
A practical hand-off includes the date, local time and named time zone, plus whether the time is the start or stop. This prevents a common planning error: the operator and the person monitoring the encoder agree on the clock time but are thinking in different zones. If the event is important, have a second person read back the schedule details against the channel’s own programme plan.
Use Go live later for a future start
For a simpler future start, Wowza calls the workflow Go live later. Its purpose is to schedule the stream to start on a future day and time. Use it when the main task is setting a future start, rather than building a recurring pattern or a more detailed start-and-stop plan.
Do not read “Go live later” as a promise that a source will appear at the appointed time. Arrange for the encoder or camera to be ready and sending the expected input, and allow time to check the connection before viewers are due. If your workflow includes an event on YouTube as well, verify the destination and event settings separately; the Wowza schedule and YouTube’s event setup are related but distinct pieces of preparation.
For a daily meditation session, a recurring schedule may better match a regular timetable; a one-off special or a future first broadcast may suit Go live later. This daily guided meditation scheduling guide can help you think through the channel calendar on YouTube’s side. Decide which system owns each task, write down the responsible person, and avoid assuming one scheduled start will create every other part of the event.
Monitor the event in Stream Health or Monitor
During the broadcast, return to the live stream details page and use Stream Health to view connection and transcoding information. The details page also provides a real-time preview and statistics for connection, transcoding and delivery. Wowza’s current documentation says those details-page metrics refresh every 10 seconds; that is a page-specific refresh interval, not a promise that every brief fault will be captured.
The health view can graph actual inbound bitrate, frame rate, keyframe interval and frame size. Compare the incoming values with what you expect from your encoder, but distinguish actual measurements from configured settings. Inbound bitrate is what Wowza receives, and it can differ from the bitrate you set at the source. A mismatch is a prompt to inspect the source and path, not by itself a complete diagnosis.
Wowza also documents an account-level Monitor view that gives an at-a-glance picture for up to three active streams, including inbound connection status and source measures, with a link into a stream’s health view. Because the Monitor documentation is labelled legacy, confirm the current account’s labels and available controls before relying on a click-by-click walkthrough. The documentation notes that updates pause while the page is out of focus and resume when it regains focus, so keep it visible when using it for a live check.
Use Stream Health for the stream-specific diagnostic view and Monitor when the current account offers a useful overview of several active streams. Neither replaces a person watching the event. A graph is evidence about what the service observed, not proof that every viewer’s playback is smooth; brief irregularities may not register between refreshes. If viewers report a problem while the graph appears steady, check the destination playback and source as well as the displayed metrics.
Check source connection and ingest status
At the scheduled start, verify that the source is connected and that incoming video is being received. A schedule can be enabled and reach its start time while the encoder is off, pointing at the wrong destination, or sending an unexpected format. Check the connection status first, then examine actual inbound bitrate and frame characteristics for signs that the expected picture is arriving.
If the source is not connected, work from the sending end towards Wowza: confirm the encoder is running, its stream destination and key are correct, and its network path is available. Then refresh or revisit the relevant current health view and see whether the incoming connection changes. Avoid changing several encoder settings at once; make one deliberate correction and observe whether the received stream improves.
If connection is present but the stream is not behaving as expected, look at frame rate, keyframe interval, frame size and inbound bitrate together. A source can connect while sending unsuitable or inconsistent video. For an unattended loop, test the full path before the scheduled slot: source output, Wowza ingest, transcoding and destination playback. This guide to making a prerecorded video loop on YouTube is useful context for planning the content and broadcast path, but it does not substitute for checking your own live input.
Keep a short event log with the planned start, when the source connected, any observed interruption and what you changed. This is more useful than relying on memory after a long night. It also helps separate a scheduling issue from an encoder or delivery issue when you review the broadcast later.
Review health and audience information afterwards
After the event, select a historical health session by its start time and duration on the stream details page. Wowza’s current documentation says historical health sessions for a given stream are available for the last 90 days. Use that history to look for changes in incoming bitrate, frame rate, keyframe interval or frame size around the time a problem was reported. It can help narrow the investigation, but it cannot reconstruct every moment viewers experienced.
Health and analytics answer different questions. Health concerns the source and stream processing; analytics provides audience and delivery context, including viewer, device, rendition, country and popularity information. Current Wowza Analytics documentation describes automatic updates every 60 seconds and CSV export. Those intervals apply to analytics, not to the details page’s 10-second metric refresh, so do not treat all Wowza screens as if they update on one universal cadence.
Interpret unique-viewer reporting carefully. Wowza notes that its definition depends on identifiers such as IP address and user agent, so the figure should not automatically be compared with a different platform’s viewer count as though the terms were identical. Use analytics to understand patterns alongside health evidence, not as a substitute for verifying that the source and broadcast were healthy.
For a channel that needs the stream to continue while an operator’s computer is off, StreamNeo removes the specific burden of keeping that local machine running: you upload a video, provide the YouTube stream key, and the broadcast runs from the cloud with monitoring and automatic restart if it drops. It is YouTube-only, so it is not a replacement for a Wowza workflow whose destination or input requirements are different.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is Wowza Streaming Cloud still the current product name?
No. Wowza renamed Streaming Cloud to Wowza Video. Use current Wowza Video labels and documentation for instructions, and treat older screenshots as historical context rather than current navigation guidance.
Does scheduling guarantee that my live stream will start successfully?
No. Scheduling defines when a stream should start or stop, but the source still has to connect and send video. Check the connection and received input in Stream Health or the current Monitor view around the event.
Should I use a recurring schedule or Go live later?
Use a recurring schedule when the same stream follows a repeated pattern, with days and an effective period to configure. Go live later is the simpler choice for scheduling a future start; it does not by itself establish a recurring timetable or confirm source readiness.
What should I check if the stream connects but looks wrong?
Compare actual inbound bitrate, frame rate, keyframe interval and frame size with the output you expect from the encoder. Check the destination and source configuration, change one thing at a time, and use the health session afterwards to review what Wowza observed.