To my knowledge, nothing in the rules "overwrite existing planned actions(As in your question.) However, every time you attempt to properly delete an already scheduled rule, before you schedule a new rule, you get a similar result, and that attempt is simply ignored if it is not done. There was no planned rule Read more for more details …
See my response to "Rule to remember the date of the last user's message and the 30-day recall based on a scheduled rule" for an illustration of the deletion of scheduled tasks, using the "
schedule_deleteAs explained in this answer:
schedule_delete this is part of this rule is to ensure that previously "scheduled" reminders will be deleted when updating the data field (so that it only triggers a callback and with the most recent date).
For this to work (that you actually indicate the exact scheduled task to delete), you must specify a "
identifier", as "
(account:name)In my example, to understand how I know what in my case is the identifier of the task to delete, look at the way I've specified the (new) task to create that you want create: this is
"identifier" : "(account:name)", which is what I used as an identifier for scheduling a task.
In your case, I think using the
node's ID as part of the identifier would be a very good choice for such an identifier.