per-execution interruptible flag not piped through via flytekit

[tblom]

Motivation: Why do you think this is important?

The interruptible flag for an execution is part of an ExecutionSpec, but there is no way to set this on a per-execution basis via flytekit. See the code for ExecutionSpec.interruptible.

I would like to specify this value at runtime, but a present there appears to be no way to do this short of writing multiple workflows.

Goal: What should the final outcome look like, ideally?

I should be able to specify interruptible on a per-execution basis, just like I can specify overwrite_cache (another example of a value that is part of an ExecutionSpec).

This could be done, e.g., with an interruptible argument to FlyteRemote.execute(). (again, just like overwrite_cache)

Describe alternatives you've considered

I've considered writing alternate workflows, in which the @workflow or @dynamic specifies interruptible as either True or False, and calling the appropriate one at runtime to create either an interruptible workflow or one that is not.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

The issue you're describing about setting the interruptible flag per execution via Flytekit is not directly addressed in the provided data sources. However, there is a related discussion in this GitHub issue about setting interruptible at workflow start time, which suggests a similar need for dynamic configuration of execution parameters. This indicates a recognized need for more flexible execution settings in Flyte, but does not provide a solution for setting them through Flytekit at runtime.

Would you like more detail on the current capabilities related to the interruptible flag as per the existing data sources?

Sources:

• GitHub Issue on setting interruptible at workflow start

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[tblom]

Note that this issue talked about very much the same thing -- but the solution was to add this per-execution flag to the web form available on the Flyte Console UI. So there, you can set the interruptible flag, as well as the overwrite_cache flag. But via flytekit, you can only set overwrite_cache

[tblom]

@eapolinario Any thoughts about when this may get attention?