Error Codes
Note
This document lists common error codes and their meanings for each module of FlightHub 2, to help developers quickly locate issues. The document is continuously updated, and timeliness cannot be guaranteed. If it differs from actual runtime messages or has omissions, the messages shown in the product interface take precedence.
| Code | Description | Category | Reason | Solution |
|---|---|---|---|---|
| 219004 | Task expired: the created task time is earlier than the current time. Task execution failed and this message is shown. | Task Library | Task expired | Re-select the task execution time in FlightHub 2 |
| 219014 | Device does not belong to this project | Task Library | Dock does not belong to project, permission isolation | Check whether the dock's project matches |
| 219016 | Task is suspended; execution failed | Task Library | Task suspended | Check whether the task is suspended |
| 219018 | Task device did not respond within timeout | Task Library | Device offline or messaging connection interrupted, unable to report | 1. Check whether the dock is powered on 2. Check whether the dock network is normal 3. If not resolved, contact after-sales to retrieve logs and file a ticket for analysis |
| 219031 | Abnormal error | Task Library | ||
| 219032 | Failed to get aircraft properties: dock and aircraft not linked or no aircraft in the dock | Task Library | ||
| 219034 | Resumable-flight task created but not executed for more than three days; task expired | Task Library | ||
| 219037 | Failed to get takeoff/landing zone; cannot execute route task. Usually a server issue and cannot be resolved by the user. | Task Library | ||
| 219038 | Route task takeoff queue timeout; task failed | Task Library | ||
| 219101 | Failed to call device control service | Task Library | Device control service abnormal | Retrieve dock logs and contact after-sales for analysis |
| 219102 | Dock is offline; cannot perform flight task. Check whether the dock is powered off and its network is normal. | Task Library | Device offline or messaging connection interrupted, unable to report | 1. Check whether the dock is powered on 2. Check whether the dock network is normal 3. If not resolved, retrieve logs and contact after-sales for analysis |
| 219103 | Device does not exist (internal:212016) | Task Library | Dock does not belong to project, permission isolation | 1. Check whether the dock's project matches |
| 219104 | Device control service command does not exist (internal:212017) | Task Library | Service configuration error, command not recognized | Contact after-sales to retrieve logs and file a ticket (dock logs) |
| 219105 | Device control service send command timeout (internal:212018) | Task Library | Dock did not reply to task command within 10 seconds | Contact after-sales to retrieve logs and file a ticket (dock logs) |
| 219106 | Device control service reported task device timeout (internal:212024) | Task Library | Dock task progress not reported within timeout |
Page 1 of 81