Expose start delay in child workflow options

[bergundy]

Is your feature request related to a problem? Please describe.

The start delay functionality we recently added is only available when starting workflows from a client.
For feature parity, we should expose this option for child workflows as well.

The use case here is to prevent from having to put a long timer (months) at the top of a workflow and force maintaining history compatibility for as long as that workflow lives. This can be done today by starting the workflow from an activity but that loses the parent-child relationship and traceability in the UI.

Describe the solution you'd like

Expose start delay in child workflow options.

Additional context

First we'll need to add support in the API and server and then expose in all of the SDKs.

[ieure-cio]

Hi @lina-temporal, any chance of an update on this? I have a usecase which this would be very helpful for, which is more complicated to express with the tools currently available.

[KocKaan]

This is needed for real

[JLDLaughlin]

thank you for raising this! we agree, we want to add start delay in child workflow options for feature parity. it's not on our near-term roadmap, so no timeline to share here yet. but we will follow up on this thread once it gets picked up!