Do you plan to add Timeouts to InvokeWorkflowFile/LaunchWorkflowInteractive activities in the (near) future?
I know that it’s possible to artificially add a timeout and we have a snippet for just that, but having “native” support for it would simplify the workflows.
Just noticed that Microsoft.Activities.Extensions.Statements.InvokeWorkflow, as well as LoadAndInvokeWorkflow both have a Timeout. In theory, we could use that for the time being.
Is there any significant difference (aside of not having Interactive session capabilities and/or Isolation) in the actual functionality that should be taken into account?