Ben Haefele: No, it doesn't seem so. I've nearly gone mad trying!

The goal is to split actions on a toggle event - in English, let's say you want something to happen (eg, a notification) when a user follows another, or adds something to their favourites, but you don't want it to happen when they unfollow or remove the item from their favourites. A use-case might be a user and some posts - there is a many-to-many relationship called 'favourite posts'.

If you try the 'intuitive' route (add first, remove later)

FIRSTLY: The add to favourites:

1) Set your action to run "Sometimes..." and only when the user's favourite posts the current post.

THEN: The remove from favourites:

2) Set your action to run "Sometimes..." (in the advanced settings) and only when the user's favourite posts the current post.

When you go to to add a post, it adds it, then instantly removes it because the second workflow steps are satisfied (the user's favourite posts contains the post).

If you reverse the workflow order, then it works fine to add a post (it ignores the remove step 1, because the user's favourite posts does not contain it), but when you go to remove a post, it does so, then promptly re-adds it because the conditions for the next step (favourite posts does not contain this post) are satisfied.

Ben Haefele: Darragh explanation is a bit long but I faced the same issue with my app, and this is really basic functionality for any app including like/favorite button.