User metadata not propagated from child workflow command to child workflow's execution config

[dhiaayachi]

Expected Behavior

Like start workflow, I would expect start child workflow user metadata to end up on the execution config on the child workflow.

Actual Behavior

The user metadata only ends up on the event, not the actual child workflow

See https://github.com/temporalio/temporal/pull/5857 where user metadata propagation was added.

[dhiaayachi]

Thanks for reporting this. It seems like you are observing an issue related to the propagation of user metadata during child workflow execution. The user metadata is currently only available on the event and not on the child workflow's execution config.

This behavior is likely due to the current implementation of user metadata propagation. While the pull request you linked, #5857, introduced user metadata propagation, it might not have been implemented to propagate the metadata to the child workflow's execution config.

We are currently tracking this as a potential feature request. There are no workarounds available at this time, but we will consider this issue in future releases.

[dhiaayachi]

Thanks for reporting this issue. It looks like you are seeing a discrepancy in how user metadata is propagated for child workflows. Currently, user metadata is only attached to the child workflow initiation event, not the child workflow itself.

Here are some workarounds you can use:

• Include User Metadata in Child Workflow Input: Add the user metadata to the input of the child workflow as a field or nested object.
• Custom Query: Create a custom query on the child workflow to retrieve user metadata from the initiation event.

We are aware of this limitation and are actively exploring ways to improve user metadata propagation for child workflows in the future.