Transactional Replication Subscription job does not stop

You have setup the subscription as a continuous one. This is not a problem in itself, as the commands will be delivered as and when needed. The job will start when the SQL Agent starts and run forever.

If you want to slow down the replication of commands or have them run at a certain time only, then you need to create the subscription and mark it to run at certain intervals. This will then start the agent, run until all uncomitted commands are replicated then stop again.

You can change an existing job if you like too:

You add a schedule to that job with the frequency you require, then change the command that is started by removing "-continuous" from the end of the command string.

Similarly, to reverse this behaviour so that a job runs continuously, you add "-continuous" to the job command string (without the quotes).