Daniel Ostermeier - 26/Jan/10 08:55 PM The problem is that we lose track of the trigger generated by the cloning process. When the project is cloned, a new persistent instance is created via the scheduler. The scheduler registers the trigger with the event scheduler prior to it being saved to the database. This means that when the event scheduler sees the trigger it has an id of 0 and shortly after it receives a proper id. Later on, when we attempt to pause / whatever the trigger, we use the triggers id, and the event scheduler is lost.

Daniel Ostermeier - 26/Jan/10 10:41 PM fixed in revision 7700, pending review 543