Continuous jobs initiated but never processed

Created on 16 October 2024, 3 months ago

Problem/Motivation

Hi,

I created a number of continuous jobs and after saving a new entity, job items are created in the inactive state, and when cron fires, they are marked as "processing". They never get processed, however. The AI log also shows no prompts being sent.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

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
  • 🇬🇧United Kingdom scott_euser

    I tried this out but I cannot actually figure out how it is meant to work.

    1. I created a continuous job for umami for basic page
    2. I edited the about us basic page

    Should I expect something to happen then? I did not get to the 'in progress' you mentioned

  • 🇹🇭Thailand AlfTheCat

    Hi, the continuous jobs are triggered on cron, which is when they will move to the "in progress" state. I think auto-accept jobs needs to be turned on for that to work.

  • 🇬🇧United Kingdom scott_euser

    Ah probably that is what I was missing; will give it a shot

  • 🇬🇧United Kingdom scott_euser

    Hmmm doesn't seem to make a difference, sorry I think I don't understand the purpose of continuous jobs well enough

  • 🇬🇧United Kingdom scott_euser

    Aha I see:

    1. Create new basic page
    2. Run TMGMT core cron -> item switched from inactive to in progress
    3. Run AI TMGMT cron -> not changed from in progress to needs review
  • 🇹🇭Thailand AlfTheCat

    Yes that's it, it seems like the translation doesn't happen or gets stuck somehow. I checked the AI log and it doesn't show any prompts being sent.

  • 🇬🇧United Kingdom scott_euser

    I think we need to sort 🐛 Reduce redundant batch runner Active first so that jobs can be processed via cron/queue.

  • 🇬🇧United Kingdom scott_euser

    Yep its definitely covered by 🐛 Reduce redundant batch runner Active - once that is in place, I can confirm after a few minutes cron picks it up. TMGMT cron has to run first, then subsequently queue from this module. Queue can be controlled via for example Simple Cron module (has a setting to enable more fine-grained control of queue workers)

Production build 0.71.5 2024