Stop / kill thousands of triggered jobs

Hi,

I would like to know is there any way we can stop triggered jobs like the number in screen shot…

The number of jobs in screen shot is attached below…

Regards,
Saiteja.

Hi @saiteja8

How come you have so many pending jobs for the same process?

Im not too sure about this idea because i havent really tried it. I have only tries it for one instance…

Try looping the kill process activity and provide the process name to kill

Yeah Lahiru… this was my trail process which turned into a disaster…

On the machine side…I am using the kill process I loop to stop all triggered…

But at orchestrator level is there any way to stop these many pending jobs…?

This mistake is due to shown in screenshot


Thank you

Im not really sure what approach to take to stop all those pending jobs…

Guys @ClaytonM, @loginerror would be great i you guys could share your thoughts on this?

1 Like

:astonished::face_with_hand_over_mouth:

Have you tried using the Filter and choose “Pending” state so only that state is shown? Then, click the top checkbox to select all, and Kill.

I don’t remember if I have tried this myself. It’s possible it only selects one page at a time, rather than every page.

That’s the only way I think it could be done. If it only let’s you kill one page worth, then I guess you will need to do it page by page.

1 Like

Yes clayton…its page by page…but like that there are as many 800+ pages😔

Have a look at the Orchestrator API or at the Powershell library: GitHub - UiPath/orchestrator-powershell: UiPath Orchestrator PowerShell cmdlet library

You can write a batch or ps script which gets all jobs from a process, then calls StopJob for each one.

1 Like

Thank you @CosminV for some aliter…
i dont know this power shell… but may be this weekend is gonna be there to crack to know-how make this script possible to run to clear these 8000 processes…otherwise will take days to complete…

8000 processes… :astonished:

I thought it was 1000 something… oh boy…

You can write a robot that does these actions one by one

@saiteja8 Did you ever figure this out? I have the same issue :frowning:

Have you tried to disconnect the robot from Orchestrator, for example? That would at least stop the execution. :slight_smile:

Hi @kygillette and @saiteja8,

That is quite an unlukcy thing to have occured.

Although this would be a last resort, you can with a sparing partner (who is good at SQL) look for jobs status in the Database. This can only be done if you are running a on premises node or have full access to your Orchestrator Database for example on Azure SQL Database in the cloud. You probably can change the job state to faulted. This may however also affect your other tables so this is something to consider as well.

If you are running cloud orchestrator then as @CosminV suggested Orchestrator API can help you fix this.

Goodluck!