The options here seem a bit confusing. I'm not sure if terminating the job is the same as cancelling it. And I'm not clear on how the Should Stop activity works in this context. I'll need to review my notes to make sure I understand the right approach.
Cancelling the job and using a Should Stop activity sounds like the way to go. That gives you more control over the process and allows you to gracefully shut it down. I feel pretty good about that being the best practice.
Hmm, I'm not sure about this one. I know we can't just let the process stop on its own, but I'm not confident that terminating it is the right way to go either. I'll have to think this through a bit more.
I think the best way to stop an ongoing job in Orchestrator is to cancel it and use a Should Stop activity inside the workflow. That seems like the most direct approach.
Cancelling and using a Should Stop activity - that's the way to go. It's like putting your foot on the brake instead of just slamming the car into a wall.
Ashanti
4 months agoJohanna
5 months agoChristiane
5 months agoTiffiny
5 months agoEffie
5 months agoTammi
5 months agoCathrine
6 months agoNathan
6 months agoJosephine
6 months agoBobbye
6 months agoErasmo
6 months agoTrevor
6 months agoAleisha
6 months agoMirta
11 months agoTrinidad
10 months agoOretha
10 months agoMyrtie
10 months agoCheryl
11 months agoMaurine
10 months agoMelda
10 months agoKaycee
12 months agoJimmie
11 months agoShay
11 months agoLuis
11 months agoMarti
12 months agoFrederica
1 year agoMiles
1 year agoIvette
11 months agoVal
11 months agoAfton
11 months agoAntonio
11 months agoShoshana
1 year agoPrecious
1 year ago