Summary
The user discusses a discrepancy in how Flyte agents handle an "aborted" status, noting that Flyte recognizes "abort" at the execution level but not at the task level. They provide an example where a task can be stopped externally, which is reported back to the Flyte agent, but Flyte's propeller interprets this as a failure. The user questions whether this issue has been considered and suggests that the behavior should be adjusted to better handle this scenario. They emphasize the need to differentiate between an external abort and a Flyte-initiated abort, proposing the addition of an error message to clarify the situation. The user mentions that a colleague has started working on a solution related to this issue.