This will happen if you delete your database but not your jobs directory. Rarely a problem in production but annoying during development. The behavior should probably be to delete any pre-existing job directory with the same ID as the newly created job.
This will happen if you delete your database but not your jobs directory. Rarely a problem in production but annoying during development. The behavior should probably be to delete any pre-existing job directory with the same ID as the newly created job.