Hi all! I am facing issues with registering/running workflows on a remote cluster, getting this error:

RPC Failed, with Status: StatusCode.INVALID_ARGUMENT
        details: task with different structure already exists with id resource_type:TASK project:"project_name" domain:"staging" name:"some_task_name" version:"Eg1iLWFry-AOPcFmT5AdYQ=="

One suggested solution is to archive the existing tasks. but that didn't solve the issue. I tried deleting the workflow & tasks, but

flytectl delete

doesn't delete tasks or workflows (is this intentional ?). how to properly delete registered tasks completely (no archive)? this is critical I believe CC: @damp-lion-88352 @elegant-toddler-67101

Currently, I am not really familiar with

flytectl delete

However, I know how to trace the code. You can go to

flytectl

and search for the

delete

keyword to check if it is implemented or not. It will probably communicate with

flyteadmin

, and

flyteadmin

will delete the workflows & tasks.

We don't provide a delete API; you can only archive your tasks/workflows. We don't want you to accidentally delete the flyte entities, and hence we haven't made the API available. To resolve the error you're seeing, you'll need to modify your code or update the version if you're registering but not fast-registering.

thank you

You can but that isn't guaranteed to succeed. You'll have to do that at your own risk.

Please do not alter the db

I believe it's necessary to have delete api. a user cant just keep archiving and creating differently-named tasks and launch plans to avoid these errors. I changed the name of the task to fix the error, now I have a different error :

details: launch plan with different structure already exists with id resource_type:LAUNCH_PLAN

@important-hamburger-34837, you don't need to change the name of your task every time; you can just update the version. If you're using

pyflyte run

or

pyflyte register

, you don't need to specify a version as Flyte automatically computes one.

In pyflyte run there is no —version option

Have you modified the code when re-registering?

Yes

In pyflyte run there is no —version option

Yes.

pyflyte run

fast registers, hence there's no version.

But isnt it supposed to be automatically assigned ?

It should. I'm not sure what's happening in your case.

So i need to use run for development at least just to test things

We're adding support for envs in `pyflyte register`: https://github.com/flyteorg/flyte/issues/4092

Just to be accurate, what code do I have to change ? Workflow file?