Parent / Child workflow stuck after failover

Expected Behavior

Parent and child workflow can continue make new progress after a force failover.

Actual Behavior

The parent workflow failed to start a new child workflow and stuck.

Steps to Reproduce the Problem

T0 in source cluster:
Parent workflow records start child workflow initiated event.
Child workflow is started but not schedule new workflow task.

T1:
Parent workflow: start child workflow initiated event does not replicate to target cluster.
Child workflow: Workflow started event replicates to target cluster.

T2: failover

T3:
Parent workflow: run the start child workflow initiated command again and failed due to child workflow ID conflict.
Child workflow: Workflow started but no workflow task schedule due to the stuck parent workflow.