I am modelling a lengthy process where the same action could be triggered at different stages of the workflow life-cycle. This includes approval/rejection, cancellation by administrator, abandonment by the originator, etc.
I have been adding fault reporting to my actions but have discovered that once I do I get the error "Two SendReply activities have the same fault type but different Action". This seems like an unnecessary restriction.
For example, during the initial stages of the workflow I have an approval process (see attachment for xamlx) and later on in the process I need another approval (see second attachment).
So the only difference is that the first refers to ReferenceID0 and the second to ReferenceID1, but that's enough to trigger the error.
Making the two actions exactly the same by manually changing the Reference name to be globally identical yields a different error about names being the same so it doesn't even seem possible for the two actions to ever be the same.