I believe that happens in the case the workflow is not running, but I will check internally for more info, can you post exactly what sort of behaviour you are facing. and also, whats the average processing time of each event by the workflow containing the signal. If the target workflow is suspended ...