Hi,

I've got a rule which schedules a component to fire off based on a date field. This rule responds to new content being created / updated. When I first created it all of the appropriate rule executions appeared in the schedule queue. I've since made a small change to the rule which should have reduced the items in the schedule queue, however, it did not. I then took a more extreme step to debug this issue and I changed the content type which triggers my rule to see what would happen (all scheduled tasks should have been removed since this change now makes my conditions return false). Nothing changed in the queue, all initial tasks remain there.

Any idea whats going on here? Clearing 'all caches' did not show any change in the task queue.

Thanks

G

Comments

fago’s picture

fago
Primary language German
Location Vienna
commented
Category: bug » support
ts145nera’s picture

ts145nera commented
Category: Support request » Bug report
Priority: Normal » Critical
Issue summary: View changes

Hi,
I've found same problem, so I've explored database.
There are two tables implicated:

queue

rules_scheduler

In my case I did would delete all action planned, so I've deleted all item in "schedule", but cron run some actions at every execution time.
I've searched in queue table and I've found some rows with "rules_scheduler_tasks" as name.

I've deleted manually this row to stop old planned actions

So I think that there are bugs in action planning

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (works as designed)

Once scheduled jobs get queued up for execution, they are already in the execution pipeline and cannot be aborted or deleted any more. Imo, that's ok as they won't get queued if the schedule time is not reached.