Contrib.social

Partially completed jobs items are not resumed/ completed on cron

Open on Drupal.org →
Created on 25 September 2023, over 1 year ago

Problem/Motivation

I am using TMGMT together with the tmgmt_openai module, which is fantastic. Through continuous jobs, job items are triggering on cron runs for any new translations, which is great too. However, almost always the job items are only partially finished. I first posted this in the tmgmt_openai queue 🐛 "Zombie" job items are left unfinished in the queue if translation doesn't complete Active but maybe that was the wrong place. I added screenshots to that issue.

Most items are a mix of "in progress" and "review" or other states and never seem to resume. New job items are submitted but partially finished ones remain stuck forever. I need to manually delete them and run the jobs manually which usually completes all the translations in the batch process.

Is there another way to resubmit these job items, perhaps via a Drupal action that ECA can execute on cron runs?

Thanks in advance for any guidance.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

1.0

Component

Core

Created by

🇹🇭Thailand AlfTheCat

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

Comments & Activities

  • Issue created by @AlfTheCat
  • Comment 8 months ago →
    🇧🇪Belgium jarco

    We also have this issue in combination with tmgmt_openai
    If we select multiple nodes to be translated, only the first one will be translated. I am not sure if the cause is with tmgmt of with tmgmt_openai.
    Is there any way to resubmit those jobs?

  • Status changed to Closed: won't fix 6 months ago
  • Comment 6 months ago →
    🇬🇧United Kingdom scott_euser

    This is related to the ecosystem module not TMGMT. Note we have shifted over TMGMT OpenAI to AI TMGMT (part of the AI ecosystem) and are progressing on 🐛 Reduce redundant batch runner Active to solve this, which:

    1. adds the jobs to the queue, has the UI process the queue
    2. or when added to the queue via other action like continuous job, processes via cron
    3. or when there is a failure, queue item from UI can also be picked up via cron

    So you can follow the issue/review there. Thanks!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024