Hi Laetitia ZUMSTEIN 

Unknown said:

On some of my pretranslations, I have the "[segment already translated...source not re-sent]" appearing.

There seems to be no obvious reasons why it is doing it sometimes and some other times not. Any tip to solve it?

None at the moment.  We are trying to engage with the deepL team to work together on this problem and the other things we are seeing reported.

Unknown said:

And last but not least, is there at some point in time any project of doing it the IA-way, ie like on Lilt where changes are automatically updating the base and working on a iterative and deep learning way?

This would require an ability from deepL to accept completed translations for training, and the plugin would have to be redeveloped to look up the translations as you work and change them to suit the context of what you have already typed (also something deepL would need to support).  So I'd say the short answer for the time being is no.

Just clear the target segment (usually ALT+DEL or other shortuct, you need to check yourself, what works on your PC) and then go out of the segment and return to it.
The message will appear for ALL segments in draft status, even if these are empty. Only segments in status "Not translated" (symbol of blank page in the middle column) are sent for automated translation.
This is NOT a problem or a bug, but a feature - in the end of the day this is exactly what you pay for. DeepL does NOT get your translation back.