What's the barrier that is preventing this functionality from being enabled? It is preferred for us in many instances to go with recurring deliveries as it is difficult to be restrained by the single send option in the likely event that we send a particular email on several occasions to different audiences, but we forego profile substitution as a consequence.
If you prepare/ run the workflow with request confirmation turned on, the child message generated should allow you to test the profile substitution on it.
If you prepare/ run the workflow with request confirmation turned on, the child message generated should allow you to test the profile substitution on it.
