Fix: scheduler: assign anonymous clone instances properly

As anonymous clone history is unpacked, inactive instances are associated with
the first available instance number. This means all inactive instances share
the same number, and thus pending tasks for inactive instances can be
displayed with the wrong node.

Now, an inactive instance associated with a pending action gets its own
instance number.