HTTP Communicate Node with Branching Paths

[RussBlink]

Hi All,

I'm trying to build a workflow that ends with a single success notice sent out via an HTTP Communicate node after a branching workflow has created two proxy files from the original. It looks like this:

Single Hold.PNG (554.93 KiB) Viewed 3037 times

The hold is set to Synchronize, however once both flows have reached the node to proceed, they both call the HTTP Communicate step, so I get two notifications.

I created an alternative workflow where one branch ends and the Hold is set to wait for both output files to exist, seen here:

Alt Single.PNG (467.69 KiB) Viewed 3037 times

This solves the multiple notification problem, but I'd prefer to run it as a Sync rather than a Check for various reasons.

Is there a way to merge the branches back into one for a Hold set to Sync that will generate a single notification?

Thanks!

[emcodem]

Aye,

this post (and subsequent) describe one possible solution:
viewtopic.php?f=5&t=543&hilit=main+branch#p4664

Sure we are well aware that we need to build something in but to make it clean, we need to operate like "on the open heart" so it takes a while and some brains to deliver this functionality out of the box.
Let me know if you can live with above approach.