#1733 [BUG] Child workflows from aborted parents reporting UNDEFINED phase Issue created by katrogan Describe the bug User reports: verything from our system that has no phase looks like this

{"executions":[{"id":{"project":"sp-one-model","domain":"production","name":"fbc3v1iy"},"spec":{"launch_plan":{"resource_type":"LAUNCH_PLAN","project":"sp-one-model","domain":"production","name":"workflows.onemodel.premium_revenue.workflow.PremiumRevenueForecast_lp","version":"dfbdc72bb88978e3f2b8d0131445aa30f271dcb9"},"metadata":{"mode":"CHILD_WORKFLOW","principal":"unknown","nesting":1,"parent_node_execution":{"node_id":"premium-revenue-forecast","execution_id":{"project":"sp-one-model","domain":"production","name":"mo2b05rnm2"}},"system_metadata":{"execution_cluster":"flyte-production-regional"}}},"closure":{"abort_metadata":{"cause":"cascading abort as parent execution id [mo2b05rnm2] aborted, reason [Some node execution failed, auto-abort.]"},"created_at":"2021-04-12T20:50:18.120569115Z","updated_at":"2021-04-12T20:50:18.120569115Z","workflow_id":{"resource_type":"WORKFLOW","project":"sp-one-model","domain":"production","name":"workflows.onemodel.premium_revenue.workflow.PremiumRevenueForecast","version":"dfbdc72bb88978e3f2b8d0131445aa30f271dcb9"}}}],"token":"1"}
with the common theme being they all seem to be due to a manual abort of parent execution ( "abort_metadata":{"cause":"cascading abort as parent execution id [mo2b05rnm2] aborted, reason [Some node execution failed, auto-abort.] )

Expected behavior Aborting a parent should result in a child workflow execution phase showing as ABORTED as well Additional context to reproduce slack thread: https://flyte-org.slack.com/archives/CNMKCU6FR/p1634850738011500?thread_ts=1634845045.008600&cid=CNMKCU6FR Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte