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
3 months agoJohanna
3 months agoChristiane
3 months agoTiffiny
4 months agoEffie
4 months agoTammi
4 months agoCathrine
4 months agoNathan
4 months agoJosephine
5 months agoBobbye
5 months agoErasmo
5 months agoTrevor
5 months agoAleisha
5 months agoMirta
10 months agoTrinidad
8 months agoOretha
9 months agoMyrtie
9 months agoCheryl
10 months agoMaurine
9 months agoMelda
9 months agoKaycee
10 months agoJimmie
9 months agoShay
10 months agoLuis
10 months agoMarti
10 months agoFrederica
11 months agoMiles
11 months agoIvette
10 months agoVal
10 months agoAfton
10 months agoAntonio
10 months agoShoshana
11 months agoPrecious
11 months ago