POST to /job/every consistently 'overwrites' last job instance with same name

[sfny]

Hi, I've setup agenda-rest after a year using agenda in a monorepo. For some reason, when I post to /job/every instead of creating a new job in the db, the most recent job is removed and a new job is created with a new mongo _id.

I first noticed it in my app, but I've replicated the behavior with postman and I'm now pretty sure I've isolated it to the agenda-rest app I have running on heroku.

What am I doing wrong? Missing parameter? Uniqueness issue? Seems like it could be an issue with the job definition but there's not much to mess up there.

Any help would be much appreciated!

[Jaykingamez]

It seems that is agenda's default behaviour

There are ways to circumvent it, look at this