re-run a failed action didn't inherit parent execution id

Dear support,

If we re-run failed actions in workflow, the new separated action execution didn't inherit parent execution id, means we can't find "parent" element in the new action execution which is a lot trouble for us, since we want the new one show up in the same workflow chain.
if we use api:
/api/v1/executions/{id}/children
the new one is not able to get since it doesn't has parent.

so, my question is:

1. Is it possible to re-run current action instead create a separated one, in some scenario like, external system fix problem, and then we need re-run the failed one to get it through.
2. Is it possible to post an new API to get children by trace_context id? (seems the new actions hold the same trace id, so we can get all actions relate to trace id)

"context": {
"trace_context": {
"id_": "5966f6ff570e014c3431c471"
},
"re-run": {
"ref": "5967015f570e014771c04345"
},
"user": "st2admin"
}

Start by reviewing the rerun behavior described for failed workflow actions and the /api/v1/executions/{id}/children endpoint. Compare the proposed options: preserving the parent execution relationship or querying related actions by trace_context id. Done should include a decided API or execution-model change that keeps rerun actions discoverable in the workflow chain.