Estimated Race time, elevation

Yes, that is pacepro and indeed I read the manual beforehand maybe who don't read the message is you:

"My concerning is about what the watch estimates when it gives me a estimated finished time. Is it taking into account the elevation profile or it is a estimation in a completely flat race."

I am talking about the race estimation time in the watch that appears when you search for the next training recommendation. 
In pacepro you fix the goal and it adapts the pace every km or change in elevation but that is a different topic.

Ok, sorry. Then I did not understand your question right.

3361291 said:

I am talking about the race estimation time in the watch that appears when you search for the next training recommendation.

Still from this description I don’t really get, what you mean and how it is connected to PacePro Strategy. Can you be more specific, maybe with description in which menus you navigate and search?

I am talking about this screen:
https://gofile.io/d/aWbp7I

Recreate the race without the GPX file and see if you get a different time?

The estimate time is garbage. I added a trail race with 45km/1700 m and it estimates the same time as for a flat marathon.

I agree, it's nonsense. The v02max widget fairly realistically predicts that I can do a flat marathon in 4 hours but race widget tells me I can do a 90km ultra with 1500m elevation in 7 hours. I am using an 11 hour training plan for the race.

In fact, there's some logic inside. For the half marathon I'm having now the estimate of 1h41m, but for the upcoming race 23,4km 770m up it shows 2h31m. Seems like the elevation is somehow considered. Anyway, the predicted times are useless - that's for sure. My last race 26km 1100m up I've done in 3h00m - almost exactly what I calculated - but FR255 was predicting 2h21m for me. Totally unrealistic.