Continuing the discussion from Expected MISSION_CURRENT behavior at end of mission?:
I’ve replied to your comment to a new thread because I think it’s probably not related to the thread you posted on. Next time feel free to create a new thread for a new issue.
I guess you’re using mission planner? make sure you’re using the latest version of mission planner and of course check the altitude type selector on the command list.
If the problem persists, I suspect we will find it’s a mission planner issue so maybe you can grab a tlog and we can get MichaelO to investigate.