Destination(s) not reached

[Coooz]

Hi,

I have these destinations in a channel:

The "...via HTTP" destinations don't work well and are therefore disabled and replaced by "... with JavaScript" variations.

When I deploy the channel and reprocess one of the messages that had come in earlier, I find that the message has not touched the "Delete visitId with JavaScript" destination at all, and also none of the other "...with JavaScript" destinations. Only the Source connector is stated in the messages table:

With message 184 I temporarily enabled "Delete visitId via HTTP" and disabled its "with JavaScript" counterpart. This shows the result I expected. Switching the positions of the "...with JavaScript" and "...via HTTP" destinations has no effect.
What could be the reason the message doesn't reach the "...with JavaScript" destinations, and how do I solve it?

This is in Mirth Connect 4.4.2. Thanks in advance!

[Coooz]

Well, how easy can it be. This was the result of a Destination Set Filter in the Source Transformer. I should have switched to the "... with JavaScript" destinations there as well - simply forgot to do so.