New RunLLM response generated: >>>*# Question* Hi all. We noticed some unexpected behavior with cloud events where details were missing for non-successful phase transitions. It looks like this code block is the cause. Was this an optimization done to reduce load on the DB? # Answer The code block you referenced is part of the Flyte cloud event publisher implementation. It appears that the logic is designed to append additional information only when the workflow execution phase is "SUCCEEDED". This could be an optimization to reduce the load on the database by avoiding unnecessary data retrieval and processing for non-successful phases. However, the specific reasoning for this implementation is not explicitly documented in the provided data sources. Would you like more detail on this? Sources: - https://github.com/flyteorg/flyte/pull/5551 - https://github.com/flyteorg/flyte/pull/4790 Slack Link https://flyte.slack.com/archives/CP2HDHKE1/p1732659476.114889 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.