@bhargavis0909 If your job has started, there should be a Requestor which is running the job. You will need to find out that ID (for example BAX338D84GO4SXPN8CTGZLFUB4PUR07TZA) and interrupt it.

Try to follow these steps.

1. Open the Admin Studio > Jobs, locate your Job and Trace (see attachment Jobs.png)
2. Probably you will see a lot of steps running (see attachment Tracer.gif), the most important is to find the Requestor ID (see attachment TracerRequestorID.png), close the tracer.
3. Go to Admin Studio > Requestors, locate the requestor ID and interrupt (see attachment AdminInterrupt.png)
4. The requestor will terminate in the next step of the activity (see attachment TracerInterrupted.png)

Hope I help you.

@bhargavis0909

... and, if you want to figure out the batch requestor id that is running this job, then -

1. From admin studio locate that job and initiate trace.
2. As soon as tracing actually starts, stop the tracking.
3. At the top of tracer window, the requestor id can be found.

if the job is enabled on multiple nodes, you need to repeat these steps on such remaining nodes.

Please note that if you planning to stop a job abruptly in an environment like Production, first verify that by terminating that job mid way will not cause data loss or data corruption. If there is a chance, my suggest would be wait the job run out, as that would be a safer approach.