total trace of waypoint is too long

[MitchellMonaghan]

Our app generates a timeline mission by first building a WaypointMission then using TimelineMission.elementFromWaypointMission to turn that waypoint mission into a timeline. We then use missionControl.scheduleElements to upload the mission. We then use missionControl.startTimeline to fly the mission. We always call missionControl.unscheduleEverything before we missionControl.scheduleElements.

It seems that the sdk can return total trace of waypoint is too long at inappropriate times unless I'm missing something about this process. It doesn't seem to matter if its a larger mission or a small one. Once the sdk starts returning this error it is stuck that way. It doesn't matter if I attempt to fly another timeline that I've been able to fly before. I've double checked the distance on so of the timeline waypoints. The largest waypoint to waypoint distance is 433.13 meters and the total timeline length is 6427.51 meters. Flying a smaller timeline it still throws this error, even on timelines I've been able to fly in the past.

At some point it does seem to fix its self, but it can persist through reboots which is a pretty frustrating experience. Not sure where the issues lies as this error comes from the sdk and I have double checked the timeline generated, and clear any existing timelines.

[dji-dev]

Agent comment from yating.liao in Zendesk ticket #86873:

I would like to inquire about the model of the device you are currently using. In fact, we have provided an executor for WaypointMission. Have you considered using WaypointMission directly?

Thank you for your attention and I look forward to your response.

°°°