> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/troubleshooting.md).

# Troubleshooting

Diagnose Cloud Streaming connection, processing, playback, sink, credit, and browser-capture problems.

Check the source and the Workflow run separately. Start with the source's connection state, then select the affected run and read its error and "Activity". Avoid creating duplicate paid runs while diagnosing an existing one.

## Access is denied

Confirm you are in the intended Workspace. In the EU region, RTMP and webcam or phone sessions are not available yet.

For the app, ask an administrator to check "View Stream Processing" and "Manage Source Video". For the API, check the Workspace in the URL, the key's Workspace, and the [required scopes](https://docs.roboflow.com/reference/authentication/authentication/scoped-api-keys). OAuth tokens and device keys cannot start jobs. Folder-scoped keys work only on sources in their folders.

Do not retry an authorization failure in a loop.

## Connector is missing or offline

Follow [Install a Connector](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/install-a-connector.md) to verify the installed version, executable, configuration, and long-running process. Check that its machine remains awake, has the intended Workspace credentials, and can reach the required cloud services.

Keep the installation's persistent state when upgrading. Do not copy one installation identity into several simultaneously running connectors. For an authentication error after key rotation, update the connector's configured key and restart it using its installation instructions.

If the connector is online but a camera is not, check the camera separately. An online connector does not prove that the cloud is receiving camera frames.

## Camera has no usable video

* USB camera: check OS camera permission, whether another program owns the camera, and the selected supported capture mode.
* RTSP camera: verify reachability from the connector's machine, the camera credentials, stream URL, and selected ONVIF profile. Cloud processing cannot access a private LAN camera without its connector.
* USB capture settings: check that "Capture Settings" shows "Applied", not "Settings rejected".
* Browser playback: verify the source codec and a supported browser. A source can be connected while its encoded video is not playable in your browser.
* Direct RTMP/RTMPS: verify the exact protocol, publishing address, and current stream key. After a key rotation or disconnect, broadcast again and restart the Workflow if needed. See [Connect a Source](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/connect-a-source.md#direct-rtmp-and-rtmps).

Do not include camera passwords, private RTSP URLs, stream keys, or pairing QR codes in screenshots or support messages.

## Waiting for video or capacity

"Waiting for video" means an enabled Workflow needs usable input. Restore the source, then check whether frame statistics advance. Source absence can pause a persistent Workflow without disabling it.

"Waiting for capacity" means the required processing resources are not available yet. Starting extra jobs can add to the queue. Inspect the existing run and its error before retrying.

"Starting" can include model loading. If startup fails, use its actual error to distinguish a model or configuration problem from a capacity problem. See [processing states](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/manage-and-monitor.md#processing-states).

## Workflow is blocked or fails

Read the error before choosing a fix:

* Invalid Workflow, input, or model access: fix the configuration or permissions. Publish the intended saved Workflow before an ordinary restart.
* GPU memory: wait for an automatic size adjustment when offered. If the largest allocation cannot fit the Workflow, use a smaller model or reduce its resource needs.
* Capacity during a size adjustment: do not report the Workflow as too large solely because a larger allocation is unavailable.
* Credit limit: resolve the Workspace's credit standing, then explicitly start or restart. A refill does not automatically resume a credit-stopped deployment.
* "Recovery suspended" or "Needs attention": read "Activity" and fix the reported cause, then restart.

Restart and recovery can reset trackers, counters, and cooldown state. They do not provide uninterrupted video or replay missed frames. See [restart behavior](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/manage-and-monitor.md#restart-processing) and [pricing](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/pricing-and-limits.md).

## No annotated output or latest result

Confirm that you selected the intended run, not an older deployment or separate preview. Verify that it is processing and that frame counters advance.

For annotated video, select an image-producing Workflow output. JSON-only Workflows can run without a playable output image; inspect "Latest Result" instead. An `image_ref` entry identifies an image output but does not contain image pixels.

A live viewer can miss results while disconnected or slow. "Latest Result" and "Activity" cannot recover the full prediction or video history. Use a Workflow sink for data you need to retain.

## API playback stops after working

Keep renewing the watch. If `executionGeneration` changes, request a new watch grant and reconnect.

Check whether the job stopped or is waiting for input. Use `whepUrl`. Another viewer can change the image output for everyone.

See [Watch live output](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/consume-results.md#watch-live-output). A failed player does not stop a deployment or its billing: cancel the job when you finish.

## Webhook or notification sink sends nothing

Check that the sink is on in the running Workflow version. Publishing alone does not update a running job.

Check the filtering condition and cooldown. Use `fire_and_forget: false` during a controlled test so Webhook Sink errors are visible. Confirm that the cloud processor can reach the destination and that the receiver accepts the method, authentication, and payload. A private address reachable from your laptop is not necessarily reachable from the cloud.

See [Webhook Sink](https://docs.roboflow.com/workflows/blocks/blocks/data-storage/webhook-sink) for configuration. Keep testing separate from production notifications and side effects.

## Offline notification email is missing

Check that Workspace notifications were saved and enabled, the recipient is a Workspace member, and "Offline notifications" is on for the connector. The stream must be offline past the threshold and needed by a running deployment.

Preview-only runs, direct sources, disabled processing, and blocked Workflows are excluded. Hourly and daily caps can delay an update. No recovery email is sent. If you request a test, "accepted for delivery" does not confirm inbox delivery. See [Offline notifications](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/manage-and-monitor.md#offline-notifications).

## Capture expired or recording did not save

Temporary inspection captures expire after five minutes or page closure and do not survive reload. Ask for a new capture if the old one expired; saving cannot recreate that exact moment.

For saved recordings, keep the original conversation open and connected until the Background Task completes. A task that has only started is not a saved asset. Check for a lost source feed or missing browser MP4 support. Retrying a failed capture records a later moment.

See [browser capture](https://docs.roboflow.com/deployment/roboflow-cloud/cloud-streaming/consume-results.md#save-a-snapshot-or-clip) for supported durations and completion behavior.

## Only some streams restarted

Keep the restart dialog's reported scope. "Try Again" retries only unfinished restarts; it does not restart the successful runs again. If the old runs are still stopping, wait and retry rather than creating replacement jobs manually.

"Restart All Streams" excludes intentionally stopped streams and previews. Restart streams that stopped for resource limits from their own page.

## Prepare a support request

Include the Workspace slug, source ID, job ID, connector ID if relevant, and the time of the failure with its time zone. Add the non-secret error text, the relevant Activity entries, your OS and browser versions, and the connector version.

Describe what you expected, what happened, and whether other sources or runs are affected. State whether the issue followed a restart, key rotation, Workflow edit, or network change. Do not include API keys, playback URLs, publish keys, camera credentials, or sensitive footage. See [What to Include in a Support Request](https://docs.roboflow.com/platform/support/getting-help-faster-what-to-include-in-a-support-request).
