Paul Dittamo

@pablocasares thank you for pointing this out. Were you able to determine if the workflow was still getting executed by propeller or was it just the console showing it as...

@pablocasares My initial thoughts were this had to do with the [cache](https://github.com/flyteorg/flyte/blob/43c0f1a61b288ce150968630de3aef0fd0aa980e/flytepropeller/pkg/controller/nodes/subworkflow/launchplan/admin.go#L172) not getting updated but I'm not noticing anything while stepping through the code + looking at the updates...

@pablocasares thank you for the added info. And just to circle back/confirm, - Were you able to determine if the parent workflow was still getting executed by propeller or was...

@pablocasares thank you for the follow up. Apologies for the mix up - was just added to the slack channel. Let me look back into this.

@hamersaw yup that makes sense. I'll make a follow up PR to handle that.

> Can you fix the unit test failure? The error: > > ``` > FAILED tests/flytekit/unit/core/test_array_node_map_task.py::test_inputs_outputs_length - AssertionError: assert equals failed > 'tests.flytekit.unit.core.test_ 'tests.flytekit.unit.core.test_ > array_node_map_task.map_many_in array_node_map_task.map_many_in > puts_-6�b^3b�d0^353d�a5d^e6e�8-4d7�9-82921� puts_b^f51001578�d0^ae197�a5+2c0af0a�...

put up change for console: https://github.com/flyteorg/flyteconsole/pull/851

~fixes: https://github.com/flyteorg/flyte/pull/5680 https://github.com/flyteorg/flyte/pull/5681 https://github.com/flyteorg/flyte/pull/5451~ oops - this is the incorrect issue for these

~@cw75 we just upstreamed a few of the fixes. Will close this after https://github.com/flyteorg/flyte/pull/5681 is merged~

@pablocasares would you still have access to your propeller logs? If so, can you check if [Retrieved Launch Plan status is nil. This might indicate pressure on the admin cache.](https://github.com/flyteorg/flyte/blob/2f38d65e45b1f098393feea72d8906b5aa645ade/flytepropeller/pkg/controller/nodes/subworkflow/launchplan.go#L170)...