Hi Team, is it possible to manually mark a flyte task as succeeded/failed like Airflow? Or is there any plan to support that?

What does manually mark as failed mean? Isnt that just aborting?

It's basically the flexibility to start workflow from anywhere. Let's say we have a Workflow: Task A => B => C => D And D doesn't need input from C, it's just task dependencies, and we want to start from Task D.

is that task chaining? https://docs.flyte.org/en/latest/user_guide/advanced_composition/chaining_flyte_entities.html#chain-flyte-entities

@workflow
def wf():
  t1() >> t2()

Today not supported, but We need to enable somehow providing manual inputs

Yeah, that would nice. To correct my first msg, Airflow (also LinkedIn's Azkaban) allow this but they don't support manual inputs.

ya they have no inputs

when do we do that?

Many cases: 1. After a failure, user wants to start from the failed task and a input change. a. In this case, we ask our user to submit another flyte execution and let output caching to skip the succeeded tasks. (It's okay, but some task disabled cache) 2. Without a failure, user wants to start the workflow from task C (let's assume a wf with task A=>B=>C=>D) a. C might not have inputs needed, it can be a stateless task b. C might have a hardcoded inputs, let's say

hdfs_path=/user/biao/data/

c. C might have a inputs which is outputs of B: i. In this case, we need setup the inputs dataset using some workaround, manually change the inputs of C

Problem is we basically want to recover in manual Override mode

Ketan, we'd be definitely interested in this as this is one of the major asks from our users. We can look into collaborating on this

That’s awesome. Happy to jump on a call to discuss how I think new can do this