Skydio Integration Troubleshooting

Overview

This article covers common issues agencies run into after setting up the Skydio integration — flights not syncing, missing telemetry, hardware not appearing, mission visibility issues, and streaming/alerts not firing. These issues can occur whether Skydio is being flown on the controller or through the DFR (Drone as First Responder) platform on the web, since both rely on the same underlying data sync between Skydio Cloud and DroneSense. Most of these issues trace back to a handful of root causes: mismatched pilot emails, missing telemetry in Skydio Cloud, or a webhook/alert that wasn't fully configured on the Skydio side.

If you haven't yet set up the integration, or need to double-check your configuration, see Skydio Integration Configuration for the full webhook, alerts, live streaming, and API key setup steps.

Troubleshooting Skydio Issues

Pilot Email Mismatch

The pilot associated with a Skydio aircraft must use the same email address in both DroneSense and Skydio. If the emails don't match, flight data will be skipped entirely for that record — this includes any Skydio flight with no pilot assigned.

• Check if any new users have been added to either system recently.
• Check if any pilot email addresses have been changed in DroneSense or Skydio.
• Confirm the pilot's DroneSense profile email matches their Skydio account email exactly (typos, aliases, and domain differences all count as mismatches).

No Missions Found on Skydio Controller

If selecting a mission on the Skydio controller shows "No missions found. Contact your organization admin for assistance," work through these checks:

• Sign in to DroneSense and check the list of Missions in Operations Hub. If no Missions appear at all, the pilot's profile settings — specifically their Team assignment — may be limiting which Missions they can see.
• Check that the Missions are not expired. Expired Missions won't appear in the controller's selector.

Missions Missing from the Mission Selector

If specific Missions are missing rather than the whole list being empty, check that those Missions are not expired.

Flights Not Syncing / Missing Telemetry

If Skydio flights aren't appearing in DroneSense, work through these checks in order:

1. Confirm the flight log and telemetry were actually uploaded from the drone/controller to Skydio Cloud. In Skydio Cloud's flight history, the record should show flight time, flight location, and pilot name. If any of these are missing, DroneSense cannot process the flight.
2. Check whether the flight has an address/location in Skydio Cloud. Flights with no location data have no usable telemetry and will not be processed into DroneSense — this is expected behavior, not a bug.
3. Verify the pilot email matches in both systems (see Pilot Email Mismatch above) — this is the most common cause of "missing" flights.
4. If telemetry is missing in Skydio Cloud, contact Skydio Support to resolve it on their end — DroneSense has nothing to process until the telemetry exists.
5. If logs and telemetry are present in Skydio Cloud but still not showing in DroneSense, load historical flight logs manually: go to Admin > Settings > API Integrations and click Load Historical Skydio Flights.

Webhook / Alert Misconfiguration

If live streaming or telemetry isn't arriving in OpsHub, the issue is usually in the Skydio-side Webhook or Alert setup rather than DroneSense.

• Confirm both webhooks exist in cloud.skydio.com > Settings > Developer > Webhooks: one named DroneSense Video pointing to https://external.dronesense.com/v1/externalintegrations/skydio, and one named DroneSense Telemetry pointing to https://external.dronesense.com/v1/externalintegrations/skydio/telemetry.
• Confirm both Alerts exist under Settings > Alerts: DroneSense Live Stream (event type: Live Stream Status Changed) and DroneSense Telemetry (event type: Flight Telemetry Available) — and that each has its matching Webhook toggle enabled and pointed at the correct webhook.
• Check that the Alerts are scoped to the right drones or to the entire organization — an alert scoped to the wrong aircraft will silently not fire.
• Confirm Live Streaming > Live APIs shows both the RTSP Streaming and Live Telemetry sections, and both are toggled on. If either section is missing entirely, Skydio Support hasn't enabled that feature for the account yet — this needs to be resolved on their end.

Hardware Not Appearing After Flights

Aircraft hardware records populate in DroneSense only after processing a completed flight, so missing hardware is usually a symptom of one of the sync issues above rather than a separate problem. If a new Skydio drone isn't showing up as hardware after flights, work through these checks:

• Each aircraft must have been flown at least once, with the flight fully processed into DroneSense, before it will appear as hardware.
• Confirm the flight log and telemetry were uploaded to Skydio Cloud. The Skydio Cloud flight history should show flight time, flight location, and pilot name — if any of these are missing, DroneSense cannot process the flight log or telemetry, and the aircraft will not appear.
• If the logs and telemetry are available in Skydio Cloud but the aircraft still isn't populated in DroneSense/Axon Air, load historical flight logs as described in Adding a New Skydio Aircraft to Your Account.
• Once a flight has processed, check the aircraft's hardware page for the Onboard Device Registration section — if it's not there, the flight likely didn't fully process (revisit the checks above).
• If multiple Skydio API keys are configured for the org, confirm the aircraft's flights were pushed under a key that's still active in Admin > Integrations > Skydio.