Incorrect 'Missed Turnpoint 1' error on task declaration

[apm2000g]

For this flight https://www.weglide.org/flight/370866 the task reports as 'Missed Turnpoint 1', but it appears to be clearly rounded. XCSoar recorded the turnpoint met in flight and also the task completed. Any reason why WeGlide thinks this was not flown correctly?

[deltafox44]

@apm2000g 'Keyhole' tasks have a start line (a beer can only at finish), and the start line was missed (crossed only in tow, as shown below).

This is a good reason why the task was not 'rounded', though the report should be 'No start' instead of 'Missed Turnpoint 1'

[moldhouse]

The problem is that the task was indeed started (at the end of the flight). So formally, turnpoint 1 missed is correct. But our error message is misleading and we'll try to improve it.

[deltafox44]

Sorry I did not notice the start just before landing ;-)

The error message is not misleading, but when it is not obvious
it may be difficult to find why the reason why it was missed.

It would be good to develop the error message giving clues to what was completed or missed. In this case something like "Start à 08:16 at 456 m MSL" & "Last fix at 08:17 at 30 km of TP1" would help understanding. In any other miss cases (TP sector missed by a few meters, more than 1000 m difference between start and finish, etc.) It would help too...

It could be added to "Statistics/Task" tab. As said on another thread these statistics should be present for each leg even when the task was not completed. Clicking on the error message "Missed TP1" could link to these statistics, rather than at present to "Why do I get no extra points for my declaration?".