New RunLLM response generated: >>>*# Question* I've got a workflow in a hung state. It has a dynamic task with a sub-workflow. When I click into the sub-workflow, it shows as completed successfully, but the parent workflow still shows it as running. I've been spelunking through propeller logs this morning, one big thing standing out so far: Near the time the issues begin, I start seeing "Failed to cast contentMD5 [] to string" in the logs, which has continued at a fairly regular interval ever since it first appeared. The exec_id is that of the child workflow. (full log line in thread) # Answer The issue you're experiencing, where a parent workflow remains in a running state despite a sub-workflow completing successfully, is not explicitly covered in the provided data sources. However, similar issues related to sub-workflow status reporting and handling have been documented. For instance, there was a problem where a sub-workflow's failed state was not reported to the parent workflow, causing the parent to remain in a "running" state (source). The log message "Failed to cast contentMD5 [] to string" suggests there might be an issue with the metadata handling or state propagation between the sub-workflow and the parent workflow. This could be related to known issues with Flyte's handling of sub-workflow statuses under certain conditions. Would you like more detailed information on how similar issues have been addressed in the past? Sources: - Flyte Issue on Subworkflow Status Reporting Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1724259078.876629 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.