This now represents duplication with respect to the impl at line 342 and should be consolidated. Also the inconsistency in error strategy is peculiar - is there a reason to expect different kinds of failures with the two kinds of activities? What happens if we just rely on our standard "unhandledException" node-level handler? In general we try to avoid the use of explicit exception handling in Infusion-aware code so should try to eliminate this try block if we possibly can. Along with harmonising this it would probably also make sense to harmonise the use of the final callback argument - start and update should use a consistent approach to signalling error or success, whatever we decide on.