what to do if a job is still running in orch even after stopping in orchestrator, as if we kill it report is not generated so how
When you click “stop” in Orchestrator, it just sends a “should stop” command to the job. You have to account for this in your code with the Should Stop activity.
If the job is running for a long time you need to figure out why.
It is included in code, yet it is picking up new items and running
You don’t just use the Should Stop activity. It gives you a boolean (true/false) value back. True if a stop command has been sent from Orchestrator. You have to use logic in your code of when to check for the stop command, and what to do if it’s True.
Hi @Abh
Could you please share at what point in your process, you have included a should stop activity?
Please note:
Scenario - if you included should stop in get transaction workflow… if a queue item is in progress and you enable stop from orchestrator, it will only stop after finishing current queue item, that too if you have routed result(true) of should stop to end process.
It really matters where you have included the should stop activity and what is your next sequence of steps when its encountered.
it is in get transaction
have you enabled the flow from get transaction to end process if should stop is true?
based on the behavior you have mentioned you are experiencing, i feel you are missing this part.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.