Continuous translation jobs - retry later after API-fail/ API limit reached

Created on 30 May 2024, 6 months ago
Updated 5 June 2024, 5 months ago

Problem/Motivation

I'm using this module on cron to translate nodes in combination of the free Deepl API in a continuous job.

Once the 500.000 free characters/month are used, the translations are not processed anymore and the job Item status becomes "In progress".
I would like to know if it's possible to retry the API-call after some time, so the node gets translated when there are again free available characters.

Now I can abort the job item and start over again, but of there are a lot of nodes, this manual process can take a while.

Feature request
Status

Active

Version

2.2

Component

Code

Created by

🇧🇪Belgium stijnstroobants Leuven

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @stijnstroobants
  • 🇩🇪Germany SteffenR Germany

    Right now there is no better way to just abort the "broken" job items and start again.
    Feel free to post a MR dealing/ fixing the issue or make suggestions how this issue should be fixed.
    I'm not dealing that much with continous jobs in projects we are using tmgmt_deepl.
    The issue is kind of mix between DeepL API limits (free version) and the continous job handling of the tmgmt module.

  • 🇩🇪Germany SteffenR Germany
Production build 0.71.5 2024