Hi Serena Falconi 

That is not a problem it's a feature, one that's designed to save you money.  But if you want to resend them then use this option in your settings:

Dear Serena Falconi 

There area couple of things here.  First of all I'm pretty sure the plugin has been updated a couple of times in that space.  You can keep on top of updates by using the RSS feed for the appstore or following the #sdlappstore twitter hashtag.  The RSS feed is this:

https://appstore.sdl.com/language/language-solutions.rss

The second thing is that this plugin comes up a lot in here and if you search and review other posts you would see that there are two problems we are having to deal with.

1. The plugin is based on an API that is maintained by DeepL.  If they change something within the API then it's possible that the plugin will fail from one day to the next without us doing anything.  This is a problem we are working with DeepL to try and resolve.  The resolution when this happens could be that we have to try and fix it in the plugin, or DeepL have to fix it in the API... depends on the problem.
2. We may have a problem with the plugin and then we need to fix it.

You can send me a file you have problems with today, and tomorrow you may have problems with a new file and different set of circumstances.  So yes, it is possible that you must send over whatever file you are having problems with IF you want me to investigate it.  Otherwise I'd recommend you just make sure you always have the latest plugin installed and wait until it just works.

The alternative of course, because the DeepL plugin is not part of Studio, it's a free plugin that we have provided to our users so they can use DeepL if they wish is that you find a developer who is happy to look at this because we opensource the code so anyone can provide a fix.  But I think they will have exactly the same problem.  It's not all down to the plugin itself.

I would also recommend that if you do keep taking the different versions that you keep them somewhere safe.  We made a change to fix a problem this week and the fix "apparently" caused more issues than were previously resolved.  The reason for this is that the API has changed and I say "apparently" because when we tested with the old one it is also broken now... the API again.

So I can only tell you that we are not solely responsible for the success or failure of this plugin in Studio, but we are trying to react as quickly as we can whenever we can identify the next problem.

Dear Paul 

just to let you know and to give you some positive feedback:

After getting bad results with version 3.4 I downgraded to 3.2 and it works perfectly fine (except for the smaller issues like tab characters and text between < and >).

I tested it again with various test documents I created over the time and I can't see any differences compared to the results over the last few weeks.

So, in my case, version 3.2 works as good as alyways.