I have a failed workflow that I for some reason had an error

Question

I have a failed workflow that I for some reason had an error that just said unknown I stopped the workflow so i could restart it and it now doesnt even have the relaunch recover options

Louis DiNatale · Answer

I have the ability to recover the sub job which i have started but the main workflows UI is broken or i dont understand something

Ketan (kumare3) · Answer

Is it possible to inspect the console seems like a Ui bug

Louis DiNatale · Answer

A lot of 501s and 404s

Louis DiNatale · Answer

Does recovering the lower job stop me from being able to continuing the parent job

Louis DiNatale · Answer

I do notice the parent workflow duration is going up

Louis DiNatale · Answer

though it simply says failed

Louis DiNatale · Answer

oh actually it says failing

Ketan (kumare3) · Answer

Sorry not following seems remote workflow failed

Louis DiNatale · Answer

Yes the workflow failed I want to recover this option is not available

Louis DiNatale · Answer

I do notice that unlike all the other failed workflows this workflow has a status of failing

Louis DiNatale · Answer

instead of failed

Louis DiNatale · Answer

I think it has to do with the fact that i terminated teh job from the sub job

Louis DiNatale · Answer

How does one force a workflow to fail In its current state our workflow is stuck with failing

Ketan (kumare3) · Answer

So it s not a Ui bug

Ketan (kumare3) · Answer

Why is it stuck

Ketan (kumare3) · Answer

Is the crd still There

Ketan (kumare3) · Answer

If the crd was deleted then the only option is for I mark it deleted in the db

Louis DiNatale · Answer

The crd is still there Sorry im all over the place this has been a long set of nights Yes not a UI bug seems to be stuck after i selected terminating

Louis DiNatale · Answer

the exact error from the workflow is ```failed at Node relative finder RemoteChildWorkflowExecutionFailed launchplan fl3afrmg1jj1to aborted caused by launchplan execution aborted```

Louis DiNatale · Answer

Is there a way to make that job go to failed so i can recover

Louis DiNatale · Answer

What causes a failing status to appear

Louis DiNatale · Answer

Is there anything i can do

Louis DiNatale · Answer

I have searched the flyte repo looking for failing as a status and I dont see it outside of a boilerplate e2e test

Louis DiNatale · Answer

Is there nothing I can do here

Louis DiNatale · Answer

this is a fairly large problem for us

Louis DiNatale · Answer

We are currently in the failing state and we need to get to the failed state something has our workflow stuck What can I check what can I do what options do i have

Louis DiNatale · Answer

``` json exec id akwqvqkqc87mndj8vwrv ns e2e workflows development routine worker 25 level warning msg Workflow namespace e2e workflows development name akw qvqkqc87mndj8vwrv has already been terminated ts 2022 11 22T15 29 30Z ```

Louis DiNatale · Answer

Wow the flyte team is so responsive even when i was being fairly annoying Thank you for the effort everyone

Louis DiNatale · Answer

^ this is not sarcasm

Kevin Su · Answer

Seems like a bug in the backend Only remote workflow was failing Does any other job fail

Louis DiNatale · Answer

Dan Hammer is currently taking a look at it

Kevin Su · Answer

Is possible abort the remote workflow on the UI

Kevin Su · Answer

Great

Louis DiNatale · Answer

No you cant

Louis DiNatale · Answer

it seems to have just got a little out of sync

Louis DiNatale · Answer

which has led it to staying in the failing state