yikes  silly me you re right  i missed that change somehow  could we update the docstrings of such methods to explain that if a port is more than once in the list  that means we expect the event to happen twice  or three or n times i guess that is the current behaviour  right thanks for the patience rossella 