# Old job config keeps triggering

**URL:** <https://community.jenkins.io/t/old-job-config-keeps-triggering/35858>\
**Category:** Using Jenkins\
**Tags:** question\
**Created:** [November 25, 2025, 3:45pm UTC](https://community.jenkins.io/t/old-job-config-keeps-triggering/35858 "2025-11-25T15:45:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pwolla](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@pwolla](https://community.jenkins.io/u/pwolla)\
**Post date:** [November 25, 2025, 3:45pm UTC](https://community.jenkins.io/t/old-job-config-keeps-triggering/35858/1 "2025-11-25T15:45:30Z")

</div>

Jenkins setup: Jenkins 2.462.3

Hi,

I have a job, triggering every 5 minutes.  
I changed the script in the ‘Build steps/Command’.

The new script gets executed as expected.

However, Jenkins also keeps triggering the old script. As the old script does not exist anymore, and I find this in my logging “sh: ./xxx.ksh: No such file or directory“

I then renamed the job on Jenkins, but I see the old job name is generated again in the \<JENKINS\_HOME\>/workspace and \<JENKINS\_HOME\>/jobs folder.  
A job ID folder is created for every run.

How can I stop/cleanup ghost jobs like that?

Thanks

---

<div class="post-metadata">

**Author:** ![YetErik](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/yeterik/32/17013_2.png) [@YetErik](https://community.jenkins.io/u/YetErik)\
**Post date:** [November 26, 2025, 10:16am UTC](https://community.jenkins.io/t/old-job-config-keeps-triggering/35858/2 "2025-11-26T10:16:13Z")

</div>

I run my jobs through an SSH agent, and when I notice anomalies—for example, the jobs using an old version of a file—I simply delete both the job folder and the job@tmp folder from the workspace.  
These folders are then recreated automatically, but with the current configuration.

If you’re okay with deleting these folders, I think this might solve your problem.

---

<div class="post-metadata">

**Author:** ![pwolla](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@pwolla](https://community.jenkins.io/u/pwolla)\
**Post date:** [November 26, 2025, 10:34am UTC](https://community.jenkins.io/t/old-job-config-keeps-triggering/35858/3 "2025-11-26T10:34:58Z")

</div>

Thanks for your reply.

I already deleted the job folders in \<Jenkins\_HOME\>/jobs and \<Jenkins\_HOME\>/workspace directories.  
Indeed, they are recreated the next time the ghost job triggers, but there is no config.xlm present.

I also tried renaming the Job. Now I have the renamed job being executed, but the old job also keeps executing. Since the old job executes config tries to execute a non-existing script, the old job doesn’t do anything anymore.