Troubleshooting

​

Remote live is missing

1. Confirm the pilot device has validated internet and the mission is active.
2. Open Pilot console → Mission and check remote-live status.
3. Tap Start remote live if automatic setup was skipped or failed.
4. In Mission Overwatch, open the active mission and select Live stream (WebRTC).

The current public Copilot workflow does not present a Local Network mission button. If your Android deployment exposes Live Overwatch Screen, keep both devices on the same reachable Wi-Fi, connect by scan or device IP, and trust the relay certificate if prompted.

​

Mission Viewer cannot see the mission

1. Confirm the viewing device has internet.
2. Confirm AlphaRelay Copilot is activated with a valid license for the same organization as the mission.
3. Confirm the mission is still active. Closed missions do not appear in the viewer list.
4. Tap Refresh in the mission picker.

If timeline events appear but video does not, the pilot’s remote Live stream (WebRTC) has not started or is not ready. Restore pilot-device internet and retry remote live from Pilot console → Mission.

​

Cloud sync delayed

1. Confirm you are signed in.
2. Move to validated internet. Copilot video uploads resume through the durable device queue; browser work still needs its tab open.
3. Do not refresh during pending sync.

​

A new mission will not start

Copilot blocks a new start while an active mission, capture service, or unfinished recording still needs closeout. On Android, use Close Active Mission on the startup screen. On iOS, reopen the active mission and use Stop and complete mission. Keep the app open while capture finalizes and pending evidence is handed off, then start the next mission. Do not force-stop or reinstall the app to bypass this guard; doing so can delay recovery of the existing mission recording.

​

Footage queued or not playing

1. Keep the pilot device powered on and restore validated internet.
2. If Android Copilot opens with a queued-video panel, let it run or use Skip for now and start new mission only when field work cannot wait. On iOS, use Sync pending items or Sync now and keep Copilot open during handoff.
3. Tap Upload now if shown.
4. Wait for Loading playback link to clear in Mission Overwatch.
5. For an optional recording: confirm you are signed in and online, the file is MP4 or MOV, the correct source is selected, and no other upload is running.

Manual browser uploads do not queue before starting — retry when online. Current Controller Screen Capture missions produce one continuous recording. If a legacy mission contains adjacent chunks, ordinary Mission Footage playback should continue through recognized neighbors. A separately restarted capture remains separate. If a legacy chunk does not continue, reload the current app version, confirm the next chunk uploaded, and reopen the first chunk. If an optional aircraft or goggles recording is out of sync, choose Align with AlphaRelay capture…, match a recognizable moment in both videos, and save the offset. Suggest from recording times is only a starting point; transferred files can have misleading modification dates.

​

Controller Screen Capture did not start

1. Confirm the pilot device is an Android drone controller with AlphaRelay Copilot installed.
2. Start the mission from Choose Scenario → Start Mission. On an integrated Android drone controller, Controller Screen Capture is automatic; on a detected DJI SDK-controller setup, select Controller Screen Capture — Recommended.
3. Approve the Android screen capture prompt.
4. If voice relay is needed, grant microphone permission and confirm speech recognition is available.
5. If the app cannot be installed, allow the browser or file manager to install unknown apps. Android Developer mode is not required.

The controller’s native flight app remains the flight control app. AlphaRelay aircraft command buttons are intentionally disabled in Controller Screen Capture.

​

iPhone or iPad capture did not start

1. Confirm the device runs iOS 26 and the organization-provided AlphaRelay Copilot app is current.
2. Start the mission, open the ReplayKit broadcast picker, and choose AlphaRelay Capture.
3. Start the broadcast, then open the flight app. If capture stops, return to Copilot and tap Choose display and start capture.
4. Check iOS Screen Recording restrictions and available storage. Grant microphone permission only when microphone audio or voice events are needed.

ReplayKit must be verified on a physical device. A Simulator test does not prove controller-screen capture or background handoff.

​

Pilot mode stays locked

1. Confirm AlphaRelay detected the DJI SDK remote-controller setup and displays the capture-mode chooser.
2. Select Pilot mode, open the 12-aircraft list, and confirm the exact aircraft family is listed.
3. Tap My drone is listed — Use Pilot.
4. Power on and connect the aircraft and controller, then wait for AlphaRelay’s live flight-controller check.
5. Start only after AlphaRelay reports Supported aircraft confirmed. Pilot mode is ready.

If the aircraft is not listed, the DJI SDK is unavailable, or the connection check times out, select Controller Screen Capture — Recommended and use the native flight app. Do not rely on Pilot mode until the same aircraft, controller, payload, and firmware combination has been validated in training.

​

DJI Avata Goggles Mode did not start

1. Confirm DJI Fly and AlphaRelay Copilot are installed on the same Android device.
2. Power on and link the DJI Avata, compatible DJI Goggles, and their compatible controller.
3. For automatic detection, connect the DJI Goggles to the Android device with a compatible USB data/OTG cable.
4. Open DJI Fly and confirm the goggles live view appears before opening AlphaRelay.
5. If you use wireless live-view sharing, tap Choose Scenario, enable Use DJI Fly / goggles video feed, choose No scenario template, and tap Start Mission.
6. Approve the Android screen capture prompt.

If DJI Fly does not open automatically after approval, open it manually and confirm its live view is still active.

​

DJI Avata remote live or upload is missing

1. Keep the Android device connected to internet. If DJI Fly uses Wi-Fi live-view sharing, keep cellular data available.
2. Keep DJI Fly in the foreground during the mission.
3. Stop through the Controller Screen Capture notification or AlphaRelay Stop Mission button; do not force-close the app.
4. Keep the Android device powered on while queued footage remains. AlphaRelay resumes it automatically when validated internet returns; do not force-stop or uninstall the app.

​

Mission Overwatch dictation is unavailable

1. Use a browser with speech-recognition support.
2. Allow microphone access for the AlphaRelay site.
3. Check that the operating system can see a working microphone.
4. If the browser speech service needs network access, confirm the browser is online.

You can always type the event under Manual Event (fast). Dictation only fills the note; review it and click Log Manual Event to save the event.

​

Play with Events has no markers

• Confirm events exist and the correct primary clip is selected.
• Mission must be closed with footage linked.
• Secondary angles may need Adjust sync to primary.

​

AI live watch is not showing

1. Confirm the pilot started Live stream (WebRTC) and the remote live feed is visible in Mission Overwatch.
2. Confirm Mission Overwatch is online and the mission is still active.
3. Confirm AI live watch is enabled for the deployment and this mission.
4. If the status says the request timed out or failed, leave the page open; Mission Overwatch retries bounded requests automatically.

AI live watch does not run from the LAN-only relay video source and does not run after the mission is closed. If scenario or mission targets are missing, turn AI live watch on and expand Show details. Scenario targets come from the scenario saved with the mission. Enter mission-only targets one visible item per line and click Save targets; these supplement rather than replace standard detections. AI live alert banners dismiss after about three seconds. Open the Timeline if the banner disappeared before you finished reading it; the event remains there for review.

​

AI alert says approval is required

1. Open the mission Timeline in Mission Overwatch.
2. Compare the Device Live AI or AI live-watch alert with the source screenshot or footage.
3. Choose Approve alert to allow configured screenshot analysis and report consideration, or Dismiss alert to exclude it.
4. After approved analysis finishes, choose Accept as is or Review & edit for the resulting finding.

Approving the alert is not the same as accepting the image analysis. Both review steps are required before analyzed content can enter the report narrative.

​

Event total is lower than the visible Timeline

The Timeline can show pending or dismissed automatic alerts so reviewers can resolve and audit them. Official totals, playback markers, reports, exports, and evidence views count only undeleted human-created events, approved automatic alerts, and officer-reviewed AI findings. Use Approve alert, Dismiss alert, Accept as is, or Review & edit to finish the decisions.

​

Timeline says a finding needs review

1. Open the closed mission and select Timeline.
2. Compare the finding with its source screenshot or footage.
3. Choose Accept as is or Review & edit.

Accepting a finding in AI Review only moves it to the timeline. The timeline review is required before that finding can enter the AAR. Submitted or approved reports lock these controls.

​

Done — continue does not advance

1. Read the status beside the button for unresolved Timeline or AI Review items.
2. Finish the decisions you want to keep.
3. Click Done — continue and review the confirmation count. Timeline completion deletes remaining unaccepted AI candidates; AI Review completion rejects remaining undecided findings.
4. Stay online for a synced mission. If the action is unavailable, sign in again and reload the page.

A newly synced pending alert or finding reopens the affected review step even if it was completed earlier.

​

Ask AI is unavailable or cannot answer

1. Open a closed, synced mission and select AI Review → Ask AI.
2. Confirm footage, photos, or event screenshots are available and playable.
3. Keep Mission Overwatch online and confirm AI is configured for the deployment.
4. If AlphaRelay says it is preparing supporting evidence, keep the page open while it samples frames from playable footage.

Ask AI can answer only from available mission imagery. If the relevant moment is missing, obscured, low quality, or outside the sampled frames, it may report that the question cannot be answered.

​

Device Live AI is not tagging

1. Confirm Enable automatic OpenAI + local detection is on in Android Pilot console → Flight → Local AI, or confirm iOS capture and notification permission are active.
2. Start Controller Screen Capture; Device Live AI does not sample while capture is stopped.
3. Check Device Live AI status. With internet it should report cloud analysis; after a cloud or connectivity failure it should move to the on-device fallback.
4. Confirm Copilot is current and that the offline fallback model is available.
5. Grant notification permission if events are logged but direct alerts do not appear.

If the status says browser or cloud Live AI is active, this is expected coordination for the same mission. The on-device fallback resumes automatically after healthy cloud analysis stops or the short handoff expires. Review every auto-tag before treating it as an operational fact. Small, distant, dark, blurred, or partially hidden objects may be missed.

​

Report actions blocked

Check mission state and your role. Submitting for supervisor approval locks report editing, mission renaming, timeline and media changes, and AI Review actions. A supervisor can Return to draft to reopen work. Approved missions are permanently read-only and reports cannot be regenerated.

​

Operator is missing from Copilot

1. Connect the Copilot device to internet and refresh its license or reopen mission setup so the agency roster can update.
2. In Organization Settings, confirm the person has a full name and an active owner, admin, or operator role. Viewer and analyst roles do not appear in the operator picker.
3. Tap Operator — Select before starting and choose the person.

If no roster is available, AlphaRelay warns and can start without identified-operator attribution. Resolve the roster before operational use when your policy requires named attribution.

​

Import mission data did not upload files

Import mission data… is intentionally a workflow preview. It inventories filenames, paths, types, and sizes locally and ends with an ingestion plan; it does not upload file contents or change custody. Use Import mission, Add optional recording, or Upload Photos for the currently connected production workflows.

​

Offline package video won’t play

Open index.html from inside the extracted folder without moving files out. Use Chrome or Edge for large packages. On Android, opening index.html can isolate it from sibling media files. If Reconnect exported files appears, tap Choose package files and select the extracted footage, photos, and printable HTML files. You can choose files more than once when Android presents different folders separately. → Connectivity · Known limitations