I managed after playing around and modules modifying to schedule sending a birthday email to users. The scheduling happens on "User has logged in" because I have not found a more suitable trigger action.

So now I have a task in the schedule queue for the email which will take place in, lets say 6 months. Everytime a user logs in, however, the task is overwritten with an identical one. I found that useless.

Could there be a checkbox to either choose NOT to overwrite already existing tasks? Or maybe a condition that would verify whether a task with a specific name already exists?

Comments

sokrplare’s picture

sokrplare commented

Just ran into this as well. I'm wondering if maybe my rule is not getting a unique argument so it gets overwritten?

alibama’s picture

alibama commented

This is a bit of a deal breaker. How do we set up a scheduled rule to not overwrite existing scheduled tasks? This is really odd, i'm going to have students sent reminders when they sign up for a class, however each student signing up overwrites the previous student's scheduled reminder

alibama’s picture

alibama commented
Status: Active » Closed (works as designed)

ok - this is an easy fix = use tokens and put a unique value at the end of your identifier [node:nid] perhaps or some date function and it's fine.