The link above provided is really helpful, but I also wanted to point out that if you’re doing a latent action, that you want to be able to trigger multiple different pins (such as start, end, progress, failure, etc), you can setup as many pins as you want to the function with ExpandEnumAsExecs … then you pass your reference to the enum down to the LatentAction … and the LatentAction can set that enum reference to whatever value it wants and then call Response.TriggerLink in it’s UpdateOperation.
I… can’t provide source right at the moment, but… pass your Enum ref to your LatentAction constructor, store it in the LatentAction, then in LatentAction’s UpdateOperation(), set the stored Enum ref to whichever value you want to trigger, then call TriggerLink().